security-audit
Skill1 starsChanged 10 days agoApache-2.0View on GitHub
Application security audit before a release or as a periodic review - route authentication and authorization, default secrets, exposed ports, webhook signatures, sensitive-data access, logging, input validation, dependencies, monitoring. Use for "audit sécurité", "revue d'accès", "avant la prod". Read-only; GitHub repository settings belong to repo-hardening, an exposed secret to secrets-hygiene, an ongoing incident to incident-response.
- Reads credentials
192 other projects use a version of this.
Adopted by
Most recently taken up by
- argos-ci/argostheir own version, first seen Nov 9, 2026
- classroomio/classroomiotheir own version, first seen Nov 9, 2026
- dio-az/dotfilestheir own version, first seen Nov 8, 2026
- roke22/Squadratheir own version, first seen Nov 8, 2026
- qwwiwi/agentos-skills-publictheir own version, first seen Nov 8, 2026
- craigcossairt/trellistheir own version, first seen Nov 8, 2026
Used with
Projects with it also use create-stories, story-done 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.
lilangMaxSkillcreate-stories
Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.
Also in 11 projects that use this
- lilangMaxSkill
story-done
End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story status to Complete, and surfaces the next ready story from the sprint.
Also in 11 projects that use this
nicepkgSkillcommunity-led-growth
Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.
Also in 5 projects that use this
- nicepkgSkill
ph-community-outreach
Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy.
Also in 5 projects that use this
- +7 more from lilangMax
- +1 more from nicepkg
Other versions192 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 192
- ruvnet/claude-flow★ 80ksame name
- ruvnet/ruflo★ 79ksame name
- PostHog/posthog★ 40ksame name
- Donchitos/Claude-Code-Game-Studios★ 27ksame name
- cloudflare/security-audit-skill★ 18ksame name
- rommapp/romm★ 14ksame name
- kubeshark/kubeshark★ 12ksame name
- maximhq/bifrost★ 9.4ksame name
- mono/SkiaSharp★ 5.6ksame name
- MaxMiksa/Auto-Company★ 3.2ksame 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 repository10 other files it gives its agents.
- change-managementSkill
- dev-traceabilitySkill
- incident-responseSkill
- issue-lifecycleSkill
- project-boardSkill
- project-trackingSkill
- repo-contextSkill
- repo-hardeningSkill
- secrets-hygieneSkill
- skill-learningSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 173 edited versions we read keep these.
0
Distinctive
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
- Very specific: line 8
Read-only by default. No active test on a shared environment without approval.
- Very specific: line 12
Secrets: default values in .env.example, scripts, compose files, inventory CSVs.
“Common” is measured: kept by at least 6 in 10 of the 173 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
Security audit
Read-only by default. No active test on a shared environment without approval. Never display a secret value: cite file:line only. Read the project's security procedures first (CLAUDE.md, procedures/, docs/); "known findings" from an earlier audit must be re-verified in the code before being asserted.
Checks
- Authentication and authorization: list every route with its auth dependency; access control enforced server-side on each request (a user never reads another user's data, even by editing the request); roles and least privilege; progressive lockout after failures; error messages that do not reveal whether an account exists; no OTP or secret returned in a response.
- Secrets: default values in
.env.example, scripts, compose files, inventory CSVs; mandatory variables (${VAR:?}); no secret in the repository or logs. - Network exposure: published ports without
127.0.0.1(gateway admin, databases, monitoring, object storage), firewall, HTTPS/HSTS, CORS. - Webhooks and callbacks: signature verified on every call, constant-time comparison, replay protection with timestamp, idempotency, logging without sensitive data.
- Sensitive data (identity, phone, payment): reads and downloads logged, ownership checks, short-lived presigned URLs, masking in exports and logs.
- Input validation: server-side, parameterised queries only, rate limiting, payload size limits.
- Logging: audit of sensitive actions (who, what, when, before/after), integrity chain, no PII or secret in logs.
- Dependencies and CI: vulnerability audit, scans blocking or informative (say which), up-to-date images, security updates.
- Monitoring: real alerts (rules and recipient), business metrics, backups whose restoration has been tested.
- Money (only if the project handles it): integer amounts, idempotency, atomic debit/credit, reversal instead of edit.
Report
Table: check, result (compliant / gap / not verified), evidence (path:line), severity (critical/high/medium), action. Distinguish "verified now" from "taken from a document". Line numbers drift: re-read the code before asserting. Critical gaps open an issue (issue-lifecycle, then project-tracking) and, before a release, block the change record (change-management). Repository settings (branch protection, secret scanning, workflow permissions): repo-hardening.
Never
Silent fixes, active tests without approval, secrets in the output, "compliant" for something only documented.
End of task
Log the run: ${CLAUDE_SKILL_DIR}/../skill-learning/learn.py log security-audit ok|partial|failed [--note …].
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.