Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add IncommensurableHubris/fullstack-director --skill 07-securitygit clone --depth 1 https://github.com/IncommensurableHubris/fullstack-directorWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/incommensurablehubris/fullstack-director/07-security)<a href="https://agentmods.dev/skills/incommensurablehubris/fullstack-director/07-security"><img src="https://agentmods.dev/badge/skills/incommensurablehubris/fullstack-director/07-security/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/incommensurablehubris/fullstack-director/07-security"><img src="https://agentmods.dev/badge/skills/incommensurablehubris/fullstack-director/07-security.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00257 | $0.04251 |
| Opus 5.5 | $0.00103 | $0.01700 |
| Sonnet 5.5 | $0.00051 | $0.00850 |
| Haiku 4.5 | $0.00026 | $0.00425 |
Grade A, and why
07-security scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
07 · Security — secure
Two modes. 07-security sprint N audits one sprint's surface (post-ship or pre-ship of that slice);
07-security full audits the whole codebase (pre-release / periodic). 07 is the deep security pass: a
bounded parallel read-only OWASP panel whose findings a single sequential synthesizer reduces into
docs/security/security-audit-sprint-NN.md with a machine-readable PASS / REMEDIATE / BLOCK verdict that
06-release's G6 gates the ship on. Your graded value is not "finds vulnerabilities" — a strong reviewer
does that too (and cries wolf 68–97% of the time). It is the isolated, de-duplicated, false-positive-controlled,
machine-verdicted audit a release gate can trust: a complete OWASP partition (no area silently dropped), each
finding carrying a source_quote + a re-derived severity, read-only (the audit touched no code), routed to the
owning skill.
Operating principle — partition completely, read blind, synthesize sequentially, verdict on severity
- Panel — bounded, parallel, read-only, blind. A fixed complete partition of the OWASP areas across 4
readers (+ a conditional 5th for LLM/agentic), each seeded with only its area-slice + the code paths + a
neutral, evidence-required prompt. Leading "find the vulnerability here" framing inflates false positives;
neutral "analyze this code; cite
file:line+ the tainted source" is what controls them. Each reader is blind to the others and writes no code. Cap 3–5 (shared/subagent-protocol.md). Isolation is real only because the spawner is fresh. - Deterministic scanners under the panel. Where a runtime exists, run
npm audit/osv-scanner,gitleaks,semgrepand feed results to the owning reader — the AI panel complements deterministic tools (it catches IDOR, authz gaps, business logic they miss). Their absence is recorded, never silently skipped. - Synthesizer — one sequential reduce, never parallel. De-dupe by target, take max severity, preserve
every
source_quote, build the risk matrix, and run the completeness lens ("which area returned zero findings — clean, or under-looked?"). A parallel merge would re-amplify error. - Verdict on severity, routed; honest about limits. PASS / REMEDIATE / BLOCK keyed to Critical/High presence (below), each finding routed to its owning skill. An AI audit is not a substitute for third-party penetration testing, and live-infrastructure hardening is out of the repo audit's reach — say both, don't pretend otherwise.
What ships with it
45 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- evals/build_fixture.py 5.2 KB runs code
- evals/check_security.py 32 KB runs code
- evals/evals.json 18 KB
- evals/fixtures/app/.gitignore 28 B
- evals/fixtures/app/package-lock.json 263 B
- evals/fixtures/app/package.json 330 B
- evals/fixtures/app/src/auth.js 900 B runs code
- evals/fixtures/app/src/digest.js 944 B runs code
- evals/fixtures/app/src/server.js 1.8 KB runs code
- evals/fixtures/app/src/store.js 1.1 KB runs code
- evals/fixtures/app/test/api.test.js 891 B runs code
- evals/fixtures/base/docs/architecture/adr/ADR-001.md 668 B
- evals/fixtures/base/docs/architecture/adr/ADR-002.md 1.3 KB
- evals/fixtures/base/docs/architecture/adr/README.md 548 B
- evals/fixtures/base/docs/architecture/system.md 5.5 KB
- evals/fixtures/base/docs/planning/sprints/sprint-02.md 1.6 KB
- evals/fixtures/base/docs/quality/qa-report-sprint-02.md 1022 B
- evals/fixtures/base/docs/spec/amendment-log.json 659 B
- evals/fixtures/base/docs/spec/architecture-constraints.md 1.4 KB
- evals/fixtures/base/docs/spec/capabilities/api.md 1.6 KB
- evals/fixtures/base/docs/spec/capabilities/digest.md 1.9 KB
- evals/fixtures/base/docs/spec/capabilities/standups.md 844 B
- evals/fixtures/base/docs/spec/specification.md 2.8 KB
- evals/fixtures/beacon-sec/docs/architecture/system.md 476 B
- evals/fixtures/beacon-sec/docs/spec/agent-contract.md 1.6 KB
- evals/fixtures/beacon-sec/docs/spec/amendment-log.json 23 B
- evals/fixtures/beacon-sec/docs/spec/architecture-constraints.md 824 B
- evals/fixtures/beacon-sec/docs/spec/capabilities/research.md 2.3 KB
- evals/fixtures/beacon-sec/docs/spec/evals/research/synthesis.jsonl 153 B
- evals/fixtures/beacon-sec/docs/spec/evals/security/prompt-injection.jsonl 2.0 KB
- evals/fixtures/beacon-sec/docs/spec/specification.md 1.7 KB
- evals/fixtures/beacon-sec/src/planner.js 564 B runs code
- evals/fixtures/cases/block-arch/src/auth.js 1.1 KB runs code
- evals/fixtures/cases/block-arch/src/server.js 1.3 KB runs code
- evals/fixtures/cases/clean/.gitkeep 215 B
- evals/fixtures/cases/synthesis/src/server.js 2.1 KB runs code
- evals/fixtures/cases/vuln/package.json 368 B
- evals/fixtures/cases/vuln/src/server.js 2.2 KB runs code
- evals/README.md 12 KB
- references/agentic-panel.md 10 KB
- references/llm-agentic-module.md 4.7 KB
- references/owasp-panel.md 8.8 KB
- references/owasp-remediation.md 5.0 KB
- references/synthesis-and-verdict.md 11 KB
- templates/security-audit.md 12 KB
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 178 lines · 257 tokens per session scan A ed2404f06f3c
07-security is a skill published in the GitHub repository IncommensurableHubris/fullstack-director (5 stars, last pushed 2mo ago), licensed MIT. It adds 257 tokens to every session and 4,251 once invoked, about $0.0010 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
bmad-architecture
Work out and record the architecture decisions that keep separately built parts of a system consistent, in a short architecture document. Creates, updates, or validates one; works from a ticket file, with an existing codebase or architecture document beside it. Use when the user says "create the architecture", "create…
bmad-prd
Create, update, or validate a PRD. Use when the user wants help producing, editing, or validating a PRD.
bmad-prfaq
Test a product concept with Amazon's Working Backwards method: write the press release for the finished product first, then answer hard customer and stakeholder questions, ending in a complete PRFAQ document. Use when the user requests to 'create a PRFAQ', 'work backwards', or 'run the PRFAQ challenge'.
bmad-product-brief
Create, update, or validate a product brief. Use when the user wants help producing, editing, or validating a brief.
bmad-project-context
Set up, adopt, refresh, or audit a repository's agent instructions (the AGENTS.md block) so AI agents work well in that repo. Also records observed agent mistakes as pitfalls. Use when invoked by name.
bmad-ux
Capture the user's UX vision in two documents: DESIGN.md for how the product looks and EXPERIENCE.md for how it behaves. Use when the user says "lets create UX design" or "create UX specifications" or "help me plan the UX".