audit-security
Skill9 starsChanged 23 days agoMITView on GitHub
Application security audit. Use when auditing TLS, encryption, authentication, authorization, secrets management, incident response, SIEM, network security, or container security. Triggers on "audit sécurité", "audit security", "audit auth", "audit secrets".
- Reads credentials
16 other projects use a version of this.
Adopted by
Most recently taken up by
- tounsils/claude-code-skillstheir own version, first seen Oct 25, 2026
- VelimirMueller/ai-development-skillstheir own version, first seen Oct 25, 2026
- krixon/skillstheir own version, first seen Oct 11, 2026
- VelimirMueller/claude-skillstheir own version, first seen Oct 11, 2026
- JoseArron/skillstheir own version, first seen Oct 11, 2026
- SecurityMindedSolutions/ai-skillstheir own version, first seen Oct 9, 2026
Used with
Projects with it also use retro, implement and 2 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.
AWSSkillretro
Conduct a retrospective on a coding session.
Also in 4 projects that use this
Hugging FaceSkillimplement
Make tests pass. Invoke after /write-tests produces failing tests.
Also in 3 projects that use this
GoogleSkilltdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Also in 3 projects that use this
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 3 projects that use this
Other versions16 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 16
- kensaurus/cursor-kenji★ 9same name
- kensaurus/skills★ 9same name
- VelimirMueller/ai-development-skills★ 7same name
- VelimirMueller/claude-skills★ 7same name
- VoxTechnologies/transmute-framework★ 5same name
- daanvandenbergh/claudekit★ 2same name
- engineering-workshops/react-alicante-agentic-workflow★ 2same name
- jasonmichaelbell78-creator/sonash-v0★ 2same name
- JoseArron/skills★ 2same name
- mik2win/foureyes★ 2same name
6 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 repository59 other files it gives its agents.
- AGENTS.mdAGENTS.md
- adversarial-feature-challengeSkill
- api-contract-versioningSkill
- bug-ticket-root-causeSkill
- bug-triage-structuredSkill
- ci-pipeline-orchestrationSkill
- commit-readiness-reviewSkill
- comprehensive-test-strategySkill
- database-schema-evolutionSkill
- ddd-backend-implementationSkill
- design-system-component-lifecycleSkill
- detection-sweepSkill
- domain-glossarySkill
- domain-modeling-designSkill
- frontend-fullstack-implementationSkill
- frontend-spec-call-site-auditSkill
- merge-request-reviewSkill
- performance-profilingSkill
- recording-decisionsSkill
- recurring-bug-root-causeSkill
- refactoring-shared-component-apiSkill
- validating-features-end-to-endSkill
- visual-regression-checkSkill
- writing-robust-testsSkill
- adversarial-feature-challengeSkill
- api-contract-versioningSkill
- audit-architectureSkill
- audit-ci-cdSkill
- audit-complianceSkill
- audit-industrialisationSkill
- audit-observabilitySkill
- audit-performance-frontendSkill
- audit-qualitySkill
- audit-reportSkill
- audit-testingSkill
- bug-ticket-root-causeSkill
- bug-triage-structuredSkill
- ci-pipeline-orchestrationSkill
- commit-readiness-reviewSkill
- comprehensive-test-strategySkill
- daily-workflow-optimizationSkill
- database-schema-evolutionSkill
- ddd-backend-implementationSkill
- design-system-component-lifecycleSkill
- detection-sweepSkill
- domain-glossarySkill
- domain-modeling-designSkill
- frontend-fullstack-implementationSkill
- frontend-spec-call-site-auditSkill
- merge-request-reviewSkill
- performance-profilingSkill
- production-incident-diagnosticSkill
- qa-session-intakeSkill
- recording-decisionsSkill
- recurring-bug-root-causeSkill
- refactoring-shared-component-apiSkill
- validating-features-end-to-endSkill
- visual-regression-checkSkill
- writing-robust-testsSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
ME when: audit focused on this domain only
- Distinctive: line 15
audit-industrialisation: instead if: global multi-domain audit - it orchestrates all the audits (including ME) and produces a consolidated …
- Very specific: line 85
Read ../audit-report/reference/apparatus.md before writing the report: the score rule, the criticality and confidence levels, the handling …
“Common” is measured: kept by at least 6 in 10 of the 15 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
When ME and not audit-industrialisation
- ME when: audit focused on this domain only
- audit-industrialisation instead if: global multi-domain audit - it orchestrates all the audits (including ME) and produces a consolidated report
For a full project audit, use
audit-industrialisationrather than invoking each skill separately.
Overview
Audit the security maturity of a project: encryption in transit and at rest, key management, secrets rotation, JWT authentication, token revocation, roles and permissions, audit log, incident response plan, crisis communication, SIEM detection, patching, post-mortem, federated authentication, network security, container security. Produces a maturity score (0-4) per question.
16 questions split across 7 sections. The detailed grids (statement, checks, commands, levels 0-4) are in reference/ - see Grids by section.
Score calculation
- Sub-questions (SE-02a, SE-04a, SE-07a) count as full questions in the calculation
- A question is N/A if the project profile makes it non-applicable (see Variants by project type)
- The score rule itself is in the shared apparatus (see Report apparatus)
Audit protocol
- Identify the project type: backend, SPA frontend, fullstack, library, microservices. Mark questions N/A according to the variants below.
- Scan for secrets:
grep -rfor secret patterns in the source code - Check .gitignore:
.env, credentials, keys - Read server configs: Nginx, Caddy, Traefik, middleware headers
- Analyze auth: JWT config, refresh tokens, revocation, IdP, SSO, MFA
- Check roles: RBAC/ABAC, least privilege, separation of duties
- Review audit logs: structure, immutability, retention
- Check incident response: IRP, playbooks, crisis communication
- Check the pipeline: SAST/SCA stages, Dependabot, container scanning
- Review network security: WAF, segmentation, DDoS protection
- Review container security: images, scanning, runtime protection
- Run
npm audit(if Node.js) or equivalent for a vulnerability snapshot - Run the verification commands listed for each question
- Assign a level per question with justification and confidence level
- Produce the report using the shared output format (see Report apparatus)
Grids by section
Each file contains the statement, the items to analyze/check, the bash commands and the level 0-4 tables.
| Section | Reference | Questions | Count |
| Encryption & TLS | reference/chiffrement-tls.md | SE-01, SE-02, SE-02a | 3 |
| Secrets | reference/secrets.md | SE-03 | 1 |
| Authentication & Identity | reference/auth-identite.md | SE-04, SE-04a, SE-11 | 3 |
| Authorization & Audit log | reference/autorisation.md | SE-05, SE-06 | 2 |
| Incident response | reference/incident-response.md | SE-07, SE-07a, SE-10 | 3 |
| Detection & Patching | reference/detection-patching.md | SE-08, SE-09 | 2 |
| Network & Containers | reference/reseau-conteneurs.md | SE-12, SE-13 | 2 |
Variants by project type
Frontend SPA/PWA without a backend
- SE-02, SE-02a (DB encryption / Key management) → N/A: no server-side storage.
- SE-04, SE-04a (JWT / Token revocation) → N/A: auth is handled by the remote backend.
- SE-05 (Roles and permissions) → N/A: authorization is handled server-side.
- SE-06 (Audit log) → N/A: no server logs.
- SE-13 (Containers) → N/A if deployed on CDN/Netlify/Vercel.
- SE-01 (TLS) → adapts: TLS is terminated upstream (CDN, host). Only check that the site is served over HTTPS and that API calls are over HTTPS.
- SE-12 (Network security) → reduced: check CSP, CORS, security headers.
Library / SDK
- SE-01, SE-04, SE-04a, SE-05, SE-06, SE-07, SE-07a, SE-08, SE-11, SE-12 → N/A: not applicable to a library.
- SE-03 (Rotation) → Focus: make sure no secret is included in the published package (
npm pack --dry-run,.npmignore). - SE-09 (Patching) → stays critical: clean dependencies with no known vulnerabilities.
- SE-13 (Containers) → N/A unless the library publishes a Docker image.
Application without containers
- SE-13 (Containers) → N/A.
Report apparatus
Read ../audit-report/reference/apparatus.md before writing the report: the score rule, the criticality and confidence levels, the handling of non-auditable items and the output skeleton live there and nowhere else. Domain title Security, 16 questions: one row per code listed in Grids by section.
Exit condition
- Project type identified, N/A questions marked
- All 16 questions evaluated (or justified N/A)
- Verification commands run for each scored question
- Level (0-4) + confidence + justification per question
- Domain score computed (average excluding N/A, "X scored out of Y")
- Report produced in the output format
- Non-auditable items listed
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.

