agentleFS
ChariereFiedlerChariereFiedler/ronce-racine/skills/audit-security/SKILL.md

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

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.
  • AWSSkill

    retro

    Conduct a retrospective on a coding session.

    Also in 4 projects that use this

  • Hugging FaceSkill

    implement

    Make tests pass. Invoke after /write-tests produces failing tests.

    Also in 3 projects that use this

  • GoogleSkill

    tdd

    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

  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 3 projects that use this

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
  1. Distinctive:

    ME when: audit focused on this domain only

    line 14
  2. Distinctive:

    audit-industrialisation: instead if: global multi-domain audit - it orchestrates all the audits (including ME) and produces a consolidated …

    line 15
  3. Very specific:

    Read ../audit-report/reference/apparatus.md before writing the report: the score rule, the criticality and confidence levels, the handling …

    line 85

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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-industrialisation rather 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

  1. Identify the project type: backend, SPA frontend, fullstack, library, microservices. Mark questions N/A according to the variants below.
  2. Scan for secrets: grep -r for secret patterns in the source code
  3. Check .gitignore: .env, credentials, keys
  4. Read server configs: Nginx, Caddy, Traefik, middleware headers
  5. Analyze auth: JWT config, refresh tokens, revocation, IdP, SSO, MFA
  6. Check roles: RBAC/ABAC, least privilege, separation of duties
  7. Review audit logs: structure, immutability, retention
  8. Check incident response: IRP, playbooks, crisis communication
  9. Check the pipeline: SAST/SCA stages, Dependabot, container scanning
  10. Review network security: WAF, segmentation, DDoS protection
  11. Review container security: images, scanning, runtime protection
  12. Run npm audit (if Node.js) or equivalent for a vulnerability snapshot
  13. Run the verification commands listed for each question
  14. Assign a level per question with justification and confidence level
  15. 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.

SectionReferenceQuestionsCount
Encryption & TLSreference/chiffrement-tls.mdSE-01, SE-02, SE-02a3
Secretsreference/secrets.mdSE-031
Authentication & Identityreference/auth-identite.mdSE-04, SE-04a, SE-113
Authorization & Audit logreference/autorisation.mdSE-05, SE-062
Incident responsereference/incident-response.mdSE-07, SE-07a, SE-103
Detection & Patchingreference/detection-patching.mdSE-08, SE-092
Network & Containersreference/reseau-conteneurs.mdSE-12, SE-132

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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.