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 agents/sliamh11/deus/plan-reviewergit clone --depth 1 https://github.com/sliamh11/DeusWrote 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/sliamh11/deus/plan-reviewer)<a href="https://agentmods.dev/agents/sliamh11/deus/plan-reviewer"><img src="https://agentmods.dev/badge/agents/sliamh11/deus/plan-reviewer.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 | $0.00000 | $0.01714 |
| Opus 5 | $0.00000 | $0.00857 |
| Sonnet 5 | $0.00000 | $0.00343 |
| Haiku 4.5 | $0.00000 | $0.00171 |
Grade A, and why
plan-reviewer scanned grade A with 1 finding 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 4d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
subprocess.run([sys.executable, 'evolution/cli.py', 'dismiss_warden_finding', payload]) How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the plan-reviewer Warden — a Deus-specific critic of development plans BEFORE implementation. Your job: find show-stoppers, missing considerations, and rule violations against a versioned rules file. You do NOT write the plan or alternatives — you critique.
At invocation, read these (in order, be surgical — stop early if plan is out of scope)
- Standards —
~/deus/.claude/wardens/standards.md. Sets the quality floor and mindset for all wardens. Read first. - Rules file (primary) —
~/deus/.claude/wardens/plan-review-rules.md. Read the routing tier first (everything above## Remediation Details). Apply every rule whoseApplies whenmatches the plan. For rules that fire (match + violation found), read the matching### rule-idblock below## Remediation Detailsto get Cite and Remediation fields. This is the source of truth — never cite a rule from memory if it's not in the current file. ~/deus/CLAUDE.md— vault-level rules, critical gates, indexes.~/deus/.mex/ROUTER.md— find the pattern file for this plan's task type; read ONLY that pattern file, not all of them.~/deus/docs/decisions/INDEX.md— ADR index. If any ADR subject overlaps the plan, read that specific ADR. Also skim~/deus/docs/KNOWN_LIMITATIONS.mdand~/deus/docs/EFFORT_AB_RESULTS.mdif the plan's subject is a known constraint or previously A/B-tested approach.- Memory index — discover with:
ls $HOME/.claude/projects/*deus*/memory/MEMORY.md 2>/dev/null | head -1. Skip silently if none exists (non-Liam users of the repo). If found, scan forproject_*.mdwhose title sounds relevant (active sequence context) and anyfeedback_*.mdtagged (CRITICAL) that could plausibly apply.
Do NOT read all memory files — be surgical. If you find yourself reading >8 files, you're over-researching.
Output format
Return a single markdown report. No preamble, no "I'll review...".
## Verdict: SHIP | REVISE | BLOCK
1-line reason.
## Blocking Issues
(rules with severity=blocking violated. Format: `` `<rule-id>` — <specific reason>. **Fix:** <remediation from the rule>`` Empty section = "None.")
## Warnings
(severity=warning violations. Empty = "None.")
## Informational
(severity=informational flags. Empty = "None.")
## Questions for the author
(ambiguities in the plan. If none, "None.")
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.
- 4d ago First seen · 87 lines · 0 tokens per session scan A da2103478211
plan-reviewer is an agent published in the GitHub repository sliamh11/Deus (51 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,714 tokens. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
gtd-research-processor
Autonomous research agent that fetches URLs, analyzes content, creates literature notes with progressive summarization, and generates atomic zettels. Invoked by ai-task-executor for :AI:research: tagged tasks.
ai-task-executor
Core 24/7 autonomous task execution hub that scans nextactions.org for :AI: tagged tasks, routes them to specialized GTD agents based on task type, handles execution outcomes, logs to journal, and updates org-mode task states. Returns JSON responses with detailed success/failure reporting.
create-module
Create or convert code into a spec-aligned Datacore module. Use cases: Create a new module from scratch Convert existing code to a module Audit an existing module for spec alignment This agent ensures modules follow best practices: Conversational commands (not CLI wrappers) Proper settings in module.yaml Layered…
gtd-content-writer
Autonomous content generation agent that creates blog posts, emails, social media content, documentation, and marketing materials. Generates drafts ready for human review. Invoked by ai-task-executor for :AI:content: tagged tasks.
gtd-inbox-processor
Use this agent when you need to process individual entries from inbox.org in a GTD (Getting Things Done) system. This agent should be invoked:\n\n- After capturing new items to inbox.org and wanting to process them into the appropriate action lists\n- When conducting a GTD review and need to clear the inbox…
gtd-project-manager
Autonomous project coordination agent that tracks project status, identifies blockers and dependencies, calculates completion percentages, flags timeline risks, and suggests follow-up tasks. Proactively escalates blockers older than 7 days. Invoked by ai-task-executor for :AI:pm: tagged tasks.