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 agentmods add commands/pduggusa/judge-dredd-plugin/dredd-auditgit clone --depth 1 https://github.com/pduggusa/judge-dredd-pluginWrote 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/commands/pduggusa/judge-dredd-plugin/dredd-audit)<a href="https://agentmods.dev/commands/pduggusa/judge-dredd-plugin/dredd-audit"><img src="https://agentmods.dev/badge/commands/pduggusa/judge-dredd-plugin/dredd-audit.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.00011 | $0.00432 |
| Opus 5 | $0.00005 | $0.00216 |
| Sonnet 5 | $0.00002 | $0.00086 |
| Haiku 4.5 | $0.00001 | $0.00043 |
Grade A, and why
dredd-audit 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 5d 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
Context
- Current git status: !
git status - Recent commits: !
git log --oneline -20 - Project directory: !
pwd
Your task
Run a Judge Dredd compliance audit on this project. Check the following dimensions:
D1: Commit Compliance
- Are commit messages descriptive and conventional?
- Is there a consistent commit style?
- Are there any force-pushes or amended published commits in recent history?
D2: Corpus Alignment
- Does the project have a README?
- Is there a CLAUDE.md or equivalent project instructions file?
- Are there tests? What's the test coverage situation?
D3: Production Evidence
- Are there Dockerfiles? Do they follow hygiene (no :latest, no Alpine, platform specified)?
- Are there CI/CD workflows? Do they have proper gates?
- Is there a security policy or SBOM?
D4: Temporal Decay
- When was the last commit?
- Are there stale branches?
- Are dependencies up to date? Any known CVEs in lockfiles?
D5: Financial Efficiency
- Is the infrastructure right-sized? (Check Dockerfiles for resource hints)
- Are there unnecessary dependencies?
- Any signs of over-engineering?
D6: Democratic Sharing
- Is the project open source? What license?
- Are contributions acknowledged?
- Is documentation public and accessible?
Output Format
Score each dimension 0-95 (NEVER 100 — we guarantee 5% bullshit exists).
Provide:
- Per-dimension score and 1-line justification
- Overall score (weighted average)
- Top 3 violations (most impactful issues)
- Top 3 commendations (things done well)
- Verdict: COMPLIANT (>80), ADVISORY (60-80), or VIOLATION (<60)
Be honest. The scales know.
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.
- 5d ago First seen · 58 lines · 11 tokens per session scan A 214aeece3d17
dredd-audit is a command published in the GitHub repository pduggusa/judge-dredd-plugin (2 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 432 once invoked, about $0.0001 per session on Opus 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.