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/attilaszasz/sdd-pilotWrote 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/attilaszasz/sdd-pilot/_configuration-auditor)<a href="https://agentmods.dev/agents/attilaszasz/sdd-pilot/_configuration-auditor"><img src="https://agentmods.dev/badge/agents/attilaszasz/sdd-pilot/_configuration-auditor/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/agents/attilaszasz/sdd-pilot/_configuration-auditor"><img src="https://agentmods.dev/badge/agents/attilaszasz/sdd-pilot/_configuration-auditor.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.00017 | $0.00397 |
| Opus 5.5 | $0.00007 | $0.00159 |
| Sonnet 5.5 | $0.00003 | $0.00079 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
ConfigurationAuditor 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 2mo 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.
What it actually says
Task
Validate drafted instruction text against persisted governance configuration.
Inputs
Draft instructions, config state, and synchronization criteria.
Execution Rules
Report mismatches deterministically and avoid altering authored policy intent.
Output Format
Return sync findings with required correction actions.
1. Receive Input
- Accept drafted Project Instructions text from parent
Project Initializeragent.
2. Read Templates
- Read:
.github/skills/plan-authoring/assets/plan-template.md,.github/skills/spec-authoring/assets/spec-template.md,.github/skills/task-generation/assets/tasks-template.md,AGENTS.md. - If any file missing → mark
SKIPPED.
3. Check Alignment
- For each template check: stale principle names/numbers, changed governance rules, outdated version numbers, contradictions with new instructions.
4. Propagate Changes
- Update only outdated principle references in templates.
- Do NOT change template logic or structure.
5. Return Sync Impact Report
SYNC IMPACT REPORT
==================
Version change: <old> → <new>
Mode: <INIT|AMEND>
Modified principles:
- <principle name>: <what changed>
Template updates:
- <file path>: ✅ updated / ⚠ pending / ⏭ skipped
- <specific change made>
Follow-up TODOs:
- <any items that need manual attention>
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.
- 2mo ago First seen · 60 lines · 17 tokens per session scan A f468a95c2a26
ConfigurationAuditor is an agent published in the GitHub repository attilaszasz/sdd-pilot (98 stars, last pushed 9d ago), licensed MIT. It adds 17 tokens to every session and 397 once invoked, about $0.0001 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-30.
Other agents, from other repositories
Spec-Driven
Use the spec-driven-planner skill when the user wants implementation to be planned and approved before code changes.
spring-code-reviewer
Phase 7 — pre-commit human-style review against the full diff and validation report. Produce 08-code-review.md and final verdict; block commit on unwaived blockers.
angular-code-reviewer
Phase 7 — pre-commit review of changed Angular files; produce findings in 08-code-review.md covering correctness, accessibility, performance, security, test quality, and clarity. Use when running /review for features that touch Angular source.
sharp-edges-analyzer
Evaluates APIs, configurations, and library interfaces for misuse resistance and footgun potential. Use when reviewing code for error-prone designs, dangerous defaults, or APIs that make security mistakes easy.
swift-reviewer
Independent verifier for Swift/iOS changes. Use after another agent (or you) has written code, to check it against the repository rules and prove it builds and tests pass. Runs builds and tests and returns their real output. Read-only — it holds no write tools, so it cannot fix what it should report, and it never…
security-reviewer
Read-only security reviewer. Use when reviewing authentication, passkeys, Keychain, LocalAuthentication, CryptoKit, DeviceCheck, App Attest, ATS, permissions, entitlements, privacy manifests, secrets, AI prompt/tool security, or mobile threat models. Reports findings and does not edit code.