devs:security-core
/devs:security-core
Use when designing or reviewing authentication, authorization, secrets handling, rate limiting, or server-side HTTP hardening — and as the security lens for code review. Owns cross-language security decisions and policies; client-side browser security (XSS, CSP from the app's view, browser token storage) belongs to devs:react-core, framework mechanics to the language skills, and dependency auditing to devs:deps-core.
- Author
- aaronbassett ↗
- Repository
- agent-foundry ↗
- Licence
- MIT
- Last repository change
- 16.08.2026
Assessment and security
- Files in this package
- 7
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 16.08.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when designing or reviewing authentication, authorization, secrets handling, rate limiting, or server-side HTTP hardening — and as the security lens for code review. Owns cross-language security decisions and policies; client-side browser security (XSS, CSP from the app's view, browser token storage) belongs to devs:react-core, framework mechanics to the language skills, and dependency auditing to devs:deps-core.
Original author description
Use when designing or reviewing authentication, authorization, secrets handling, rate limiting, or server-side HTTP hardening — and as the security lens for code review. Owns cross-language security decisions and policies; client-side browser security (XSS, CSP from the app's view, browser token storage) belongs to devs:react-core, framework mechanics to the language skills, and dependency auditing to devs:deps-core.
How it works
- Reference routing
- Ownership boundaries
SKILL.md preview
--- name: devs:security-core description: "Use when designing or reviewing authentication, authorization, secrets handling, rate limiting, or server-side HTTP hardening — and as the security lens for code review. Owns cross-language security decisions and policies; client-side browser security (XSS, CSP from the app's view, browser token storage) belongs to devs:react-core, framework mechanics to the language skills, and dependency auditing to devs:deps-core." --- # Security Core Cross-cutting application-security decisions: which model, what policy, what to check. The language skills own how to express these decisions in a given framework; this skill must never contradict them — where mechanics are needed, it delegates. ## Reference routing | Reference | Use when | |---|---| | [authn-design.md](references/authn-design.md) | Choosing an auth model; token lifetime/rotation/revocation policy; MFA; CLI/desktop OAuth; password hashing policy | | [authz-design.md](references/authz-design.md) | RBAC and resource ownership; why not to hand-roll policy engines; the Postgres/Supabase RLS multi-tenant pattern | | [secrets.md](references/secrets.md) | Where secrets live, settings validation, rotation ordering, CI credentials (OIDC), scanners, key generation | | [rate-limiting.md](references/rate-limiting.md) | What to limit on which key, tiering, distributed atomicity, fail-open vs fail-closed, response contract | | [http-hardening.md](references/http-hardening.md) | Server-side canonical security headers, CSP nonce minting, CORS with credentials, HSTS | | [review-lens.md](references/review-lens.md) | Reviewing a diff for security: weighted if-the-diff-touches-X-check-Y mappings | ## Ownership boundaries - **devs:react-core** (security reference) owns client-side XSS/sanitization, the browser view of CSP and headers, and browser token storage. Server and client guidance must agree; where this skill states the server-side canonical, react-core states the client consequences. - **The language skills** (rust-core, python-core, typescript-core) own framework security mechanics — axum middleware, FastAPI auth wiring, Express setup — and the per-language library choices. - **devs:deps-core** owns dependency auditing and vulnerability scanning of the package tree. - **devs:code-review** owns the general review method; this skill supplies the security dimension via review-lens.md. This skill ships no scripts or config assets: security scaffolding rots faster than any other kind, and the language skills' verified templates are the correct home for runnable configuration.
Files in this package (7)
- SKILL.md 3 KB
- references/authn-design.md 6 KB
- references/authz-design.md 6 KB
- references/http-hardening.md 5 KB
- references/rate-limiting.md 4 KB
- references/review-lens.md 3 KB
- references/secrets.md 5 KB
Versions
The database has no other skills named devs:security-core.
Database snapshot: 13.11.2026 · package version 99cb6a3e70f1 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 80devs:code-review
Use when reviewing code changes — a diff, branch, PR, or named files. Carries the review method: scoping the change-set, converting suspicions into verified findings, and ranking by evidence-backed severity. Language idioms belong to the language skills (rust-core, python-core,… - 80devs:react-core
Use when building or debugging React applications — component and hook idioms, rendering and re-render performance, state architecture, data fetching, application security, project architecture, or choosing React-ecosystem packages. Contains runtime-verified references, a… - 100security-review
Use when assessing application code or configuration for security risks involving sensitive data, trust boundaries, authentication, authorization, input handling, secrets, or dependencies. - 100code-review-security
Security-focused code review checklist and automated scanning patterns. Use when reviewing pull requests for security issues, auditing authentication/authorization code, checking for OWASP Top 10 vulnerabilities, or validating input sanitization. Covers SQL injection prevention,… - 100client-side-security
Apply when reviewing or writing browser-facing code that handles user input, renders HTML, sets cookies, or loads third-party scripts. Covers XSS, CSRF, CSP, clickjacking, XS-Leaks, and HTTP security headers. - 100review-http-security
Use when reviewing HTTP servers, APIs, or their hosting configuration for hardening gaps, such as authentication, authorization, input parsing, uploads, CORS, headers, cookies, limits, SSRF, redirects, TLS, proxy trust, or exposed endpoints and metadata.