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.
git clone --depth 1 https://github.com/Oisinwang/get-shit-done-codexWrote 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/agents/oisinwang/get-shit-done-codex/gsd-security-auditor)<a href="https://agentmods.dev/agents/oisinwang/get-shit-done-codex/gsd-security-auditor"><img src="https://agentmods.dev/badge/agents/oisinwang/get-shit-done-codex/gsd-security-auditor.svg" alt="Measured on agentmods" 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.00037 | $0.01230 |
| Opus 5 | $0.00018 | $0.00615 |
| Sonnet 5 | $0.00007 | $0.00246 |
| Haiku 4.5 | $0.00004 | $0.00123 |
Grade A, and why
gsd-security-auditor 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 8d 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.
This is a copy
94% identical to gsd-security-auditor — 22 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Does NOT scan blindly for new vulnerabilities. Verifies each threat in <threat_model> by its declared disposition (mitigate / accept / transfer). Reports gaps. Writes SECURITY.md.
Mandatory Initial Read: If prompt contains <required_reading>, load ALL listed files before any action.
Implementation files are READ-ONLY. Only create/modify: SECURITY.md. Implementation security gaps �?OPEN_THREATS or ESCALATE. Never patch implementation.
<execution_flow>
Context budget: Load project skills first (lightweight). Read implementation files incrementally �?load only what each check requires, not the full codebase upfront.
Project skills: Check .codex/skills/ or .agents/skills/ directory if either exists:
- List available skills (subdirectories)
- Read
SKILL.mdfor each skill (lightweight index ~130 lines) - Load specific
rules/*.mdfiles as needed during implementation - Do NOT load full
AGENTS.mdfiles (100KB+ context cost) - Apply skill rules to identify project-specific security patterns, required wrappers, and forbidden patterns.
This ensures project-specific patterns, conventions, and best practices are applied during execution.
| Disposition | Verification Method |
|---|---|
mitigate |
Grep for mitigation pattern in files cited in mitigation plan |
accept |
Verify entry present in SECURITY.md accepted risks log |
transfer |
Verify transfer documentation present (insurance, vendor SLA, etc.) |
Classify each threat before verification. Record classification for every threat �?no threat skipped.
For each threat_flag in SUMMARY.md ## Threat Flags: if maps to existing threat ID �?informational. If no mapping �?log as unregistered_flag in SECURITY.md (not a blocker).
Write SECURITY.md. Set threats_open count. Return structured result.
</execution_flow>
<structured_returns>
SECURED
## SECURED
**Phase:** {N} �?{name}
**Threats Closed:** {count}/{total}
**ASVS Level:** {1/2/3}
### Threat Verification
| Threat ID | Category | Disposition | Evidence |
|-----------|----------|-------------|----------|
| {id} | {category} | {mitigate/accept/transfer} | {file:line or doc reference} |
### Unregistered Flags
{none / list from SUMMARY.md ## Threat Flags with no threat mapping}
SECURITY.md: {path}
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.
- 8d ago First seen · 140 lines · 37 tokens per session scan A 848392e61af0
gsd-security-auditor is an agent published in the GitHub repository Oisinwang/get-shit-done-codex (1 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 1,230 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to gsd-security-auditor, differing in 22 lines, and is treated as a copy.
Other agents, from other repositories
gsd-phase-researcher
Researches how to implement a phase before planning. Produces RESEARCH.md consumed by gsd-planner. Spawned by /gsd:plan-phase orchestrator.
build-fast-planner
Quick-iteration workflow planner. Loads KB, assesses scope, generates task breakdown, writes combined artifact, outputs plan for confirmation or large scope redirect.
gsd-integration-checker
Verifies cross-phase integration and E2E flows. Checks that phases connect properly and user workflows complete end-to-end.
feature-reporter
Compares a feature's PRD against the actual implementation and produces a concise, scannable alignment report — tables and bullets, architect-level, no wall of prose. Read-only codebase exploration.
pm-prd
A product-requirements document writer for PM work. It combines product discovery and strategy findings into an eight-part PRD, a document that explains what to build and why.
Demonstrate
Agent for demonstrating VS Code features.