security-review
Skill4 starsChanged 5 days agoMITView on GitHub
Review frontend and connected APIs against a selected OWASP ASVS baseline using security evidence and trust-boundary analysis. Use for application security assessments.
192 other projects use a version of this.
Adopted by
Most recently taken up by
- metacircu1ar/hive_skillstheir own version, first seen Nov 15, 2026
- 81wallace18/codex-skillstheir own version, first seen Nov 15, 2026
- FimawLLC/fimaw-skillstheir own version, first seen Nov 15, 2026
- aws/credential-daemontheir own version, first seen Nov 15, 2026
- AOSSIE-Org/Resonate-Websitetheir own version, first seen Nov 9, 2026
- dimastriann/odoo-erp-mcptheir own version, first seen Nov 8, 2026
Used with
Projects with it also use linkerd-patterns, dependency-cve-sweep and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
xfstudioSkilllinkerd-patterns
Implement Linkerd service mesh patterns for lightweight, security-focused service mesh deployments. Use when setting up Linkerd, configuring traffic policies, or implementing zero-trust networking with minimal overhead.
Also in 5 projects that use this
berntpoppSkilldependency-cve-sweep
Use when handling Dependabot PRs, CodeQL/Trivy alerts, or doing a routine dependency/CVE sweep for this repo.
Also in 12 projects that use this
- berntpoppSkill
fleet-standard-adoption
Use when bringing this repo into compliance with a GeneFoundry fleet standard (tool-naming, response-envelope, container-hardening, versioning, MCP transport, or logging) or closing its tracking issue.
Also in 12 projects that use this
HABUBUSSSkillproject-guidelines-example
Also in 16 projects that use this
niloykumarbarmanSkillagent-sort
Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.
Also in 13 projects that use this
royaluniondesign-sysSkillconfigure-ecc
Interactive installer for Everything Claude Code — guides users through selecting and installing skills and rules to user-level or project-level directories, verifies paths, and optionally optimizes installed files.
Also in 11 projects that use this
- +2 more from berntpopp
Other versions192 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 192
- affaan-m/ECC★ 246ksame name
- github/awesome-copilot★ 41ksame name
- langfuse/langfuse★ 37ksame name
- nearai/ironclaw★ 13ksame name
- joe-bell/cva★ 6.9ksame name
- doorkeeper-gem/doorkeeper★ 5.5ksame name
- github/squad★ 3.4ksame name
- compozy/compozy★ 2.9ksame name
- trycompai/comp★ 2.1ksame name
- xu-xiang/everything-claude-code-zh★ 1.9ksame name
182 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
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-buildSkill
- security-configuration-and-secretsSkill
- security-crypto-and-dataSkill
- security-dependencies-and-buildSkill
- security-diagnoseSkill
- security-injection-and-validationSkill
- security-logging-and-failureSkill
- 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
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 167 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use for an application security review or conformance-gap assessment covering code, browser, APIs, identity, deployment and relevant …
“Common” is measured: kept by at least 6 in 10 of the 167 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Review application security against a selected baseline
Scope
Use for an application security review or conformance-gap assessment covering code, browser, APIs, identity, deployment and relevant upstream services. A frontend-only review is limited-scope by definition. No penetration test is authorized merely because a review was requested.
Procedure
- Declare application, environment, component and trust-boundary scope, protected assets, identities, explicit permission for tools and chosen ASVS version/level; consult
../security-diagnose/references/standard-selection.md. - Build a requirement ledger from
../security-diagnose/references/asvs/5.0.0/index.jsonfiltered at the selected cumulative level. Resolve each applicable requirement from the pinned official ASVS 5.0.0 source, using../security-diagnose/references/asvs/5.0.0/source-access.md; if its full text is unavailable, mark it untested rather than guessing. - Inspect code/configuration and available scans, API and identity controls; load only relevant specialists. Independently evaluate higher-risk trust boundaries and NIST SSDF process gaps if requested.
- For every selected requirement record pass, fail, not applicable, not tested or needs manual verification. Require reproducible evidence for pass/fail and a documented rationale for not applicable; never infer from UI appearance or a clean scanner report.
- Prioritize verified findings by plausible impact and exposure; include owner, remediation and independent retest plan. Use WSTG 4.2 only for explicitly authorized testing methodology.
- Validate machine-readable assessment completeness using
security-validateor the distribution-side audit checker. Report incomplete coverage and untested controls rather than claiming certification.
Deliverable
Include the assessment scope, baseline/version/level, evidence sources and dates, per-requirement ledger, risk-prioritized findings, test limitations, and a short statement of what remains unknown. Security ratings are context-dependent, not derived solely from ASVS levels.
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.