security-build
Skill4 starsChanged 5 days agoMITView on GitHub
Implement secure web application, browser and API changes using OWASP ASVS 5.0.0 requirements and specialist remediation patterns. Use during frontend or connected service coding and targeted vulnerability fixes.
In this repository55 other files it gives its agents.
- design-balance-and-proportionSkill
- design-brand-and-art-directionSkill
- design-buildSkill
- design-color-theorySkill
- design-diagnoseSkill
- design-hierarchy-and-emphasisSkill
- design-imagery-and-textureSkill
- design-layout-and-gridSkill
- design-movement-and-flowSkill
- design-reviewSkill
- design-rhythm-and-patternSkill
- design-typographySkill
- design-unity-and-systemsSkill
- design-validateSkill
- security-api-files-and-realtimeSkill
- security-authentication-and-sessionsSkill
- security-authorizationSkill
- security-browser-and-originSkill
- security-configuration-and-secretsSkill
- security-crypto-and-dataSkill
- security-dependencies-and-buildSkill
- security-diagnoseSkill
- security-injection-and-validationSkill
- security-logging-and-failureSkill
- security-reviewSkill
- security-threat-model-and-designSkill
- security-validateSkill
- ux-accessibilitySkill
- ux-buildSkill
- ux-controls-and-inputsSkill
- ux-decisions-and-loadSkill
- ux-diagnoseSkill
- ux-feedback-and-performanceSkill
- ux-forms-and-errorsSkill
- ux-journeys-and-motivationSkill
- ux-navigation-and-structureSkill
- ux-onboarding-and-learningSkill
- ux-reviewSkill
- ux-trust-and-ethicsSkill
- ux-validateSkill
- ux-visual-hierarchySkill
- wcag-alternatives-and-mediaSkill
- wcag-assistive-tech-and-statusSkill
- wcag-buildSkill
- wcag-diagnoseSkill
- wcag-forms-and-error-preventionSkill
- wcag-keyboard-and-focusSkill
- wcag-language-and-predictabilitySkill
- wcag-navigation-and-discoverySkill
- wcag-pointer-and-touchSkill
- wcag-reviewSkill
- wcag-semantics-and-reading-orderSkill
- wcag-time-and-motionSkill
- wcag-validateSkill
- wcag-visual-and-responsiveSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use only for security improvements requested or needed in the authorized coding task.
- Very specific: line 15
Read matching specialist references/playbook.md and selected ASVS identifier metadata from …
- Distinctive: line 16
Prefer established project mechanisms, secure defaults, native platform protections, maintained dependencies and minimal change surface.
- Very specific: line 18
Run focused relevant tests/scans or mark them untested.
- Distinctive: line 22
Do not launch active scans against external or production targets without explicit authorization.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Implement a focused application security improvement
Scope
Use only for security improvements requested or needed in the authorized coding task. Preserve the existing architecture, release constraints and identity/security ownership. Changes to authentication, authorization or cryptography require corresponding server-side enforcement and tests.
Procedure
- Determine the protected asset, threat model, actual trust boundary, affected ASVS requirement and relevant owned code paths; distinguish user-requested scope from proposed methods.
- Read matching specialist
references/playbook.mdand selected ASVS identifier metadata from../security-diagnose/references/asvs/5.0.0/index.json; consult exact upstream ASVS requirement text before claiming satisfaction. - Prefer established project mechanisms, secure defaults, native platform protections, maintained dependencies and minimal change surface; do not introduce homegrown cryptography or authentication.
- Implement functional and negative cases for authorized/unauthorized roles, malformed input, stale sessions, errors and data exposure as appropriate. Ensure browser-only controls are not substituted for server/API enforcement.
- Run focused relevant tests/scans or mark them untested; record source diff, independent tool evidence, residual risk and rollback information. Use
security-validatefor verification.
Safe execution
Do not launch active scans against external or production targets without explicit authorization. Do not disable checks, suppress alerts, publish secrets, or broaden privileges to make tests pass. Report changes that require security-owner approval.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.