agentleFS
seancabalseseancabalse/agentic-playbook/skills/security-audit/SKILL.md

security-audit

Skill0 starsChanged 15 days agoMITView on GitHub

Audit a change or the project for security and privacy, and prove each finding. Use for auth, data, file and payment changes, and before a release.

  • Reads credentials

192 other projects use a version of this.

Adopted by

Most recently taken up by

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

    create-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

  • nicepkgSkill

    community-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

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 174 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:

    Privacy: no content in logs, analytics, crash reports or notification text.

    line 21
  2. Very specific:

    Read the diff or the code paths.

    line 28
  3. Distinctive:

    Never print a secret you find.

    line 30

“Common” is measured: kept by at least 6 in 10 of the 174 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

Playbook files named here: when the project has its own copy at .playbook/local/<same path>, use that copy instead.

Scope: $ARGUMENTS

Principles: ${CLAUDE_PLUGIN_ROOT}/principles/06-security-privacy.md. Report shape: ${CLAUDE_PLUGIN_ROOT}/templates/audit-report.md. For a new feature with no threat model yet, run threat-model first.

Check

  1. Secrets: none in the code, history, logs, fixtures or client bundles (grep for key patterns, .env committed by mistake, service keys in client config); only publishable keys client-side; CI secrets scoped.
  2. Access control: every table, view, function, bucket and endpoint is deny by default. Policies check tenant membership. security definer functions check the caller and pin search_path. Column secrets are revoked and exposed only through checked functions. Realtime publications use column lists. "Who may do what" (author-only delete) is enforced on the server. There are tests for can and can't.
  3. Input: server-side validation of types, sizes and enums; capped JSON and text; parameterised queries; no injection paths in raw SQL, shell or HTML; uploads checked for type and size.
  4. Auth and sessions: codes or platform sign-in; rate limits on sign-in, invite and join; offline isn't treated as signed out; sign-out clears queued writes, caches and push tokens; tokens are stored where scripts can't read them (HttpOnly cookies, or secure storage); deep links validate their parameters.
  5. Privacy: no content in logs, analytics, crash reports or notification text; metadata stripped from uploads; coarse location only; unused permissions blocked; export and deletion work; retention jobs run.
  6. Files: private buckets, per-tenant prefixes, signed URLs with short expiry, no overwrites, orphans swept.
  7. Abuse: rate limits with codes; quotas; idempotency, so replays don't duplicate; webhook signatures verified.
  8. Dependencies and config: advisories in the lockfile; security headers (web); debug flags off in release; cleartext traffic off; CORS allow-list.

Method

  • Read the diff or the code paths; grep for risky patterns (select * on secret tables, security definer, dangerouslySetInnerHTML, eval, string-built SQL, console.log( near user data).
  • Prove findings: write a failing access test or show the exact request. If you can't prove it, mark it plausible with the reasoning.
  • Never print a secret you find. Report its location and tell the owner to rotate it.

Output

Findings ranked Critical / High / Medium / Low, each with the exploit scenario (who, what request, what they get), evidence (file:line, test), and the fix. Add a "Checked and fine" section. Offer to file tickets; for project audits, write the dated audit doc.

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.