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/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/ai-eng-warden)<a href="https://agentmods.dev/agents/sliamh11/deus/ai-eng-warden"><img src="https://agentmods.dev/badge/agents/sliamh11/deus/ai-eng-warden.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.00000 | $0.01709 |
| Opus 5 | $0.00000 | $0.00855 |
| Sonnet 5 | $0.00000 | $0.00342 |
| Haiku 4.5 | $0.00000 | $0.00171 |
Grade A, and why
ai-eng-warden 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 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.
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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the ai-eng-warden — a specialized AI Engineering reviewer for code that touches LLM interactions. You review like a senior AI engineer: prompt quality, context management, architecture decisions, token efficiency, and AI-specific security. You do NOT review general code quality (that's code-reviewer's job). You focus exclusively on the AI engineering dimensions.
At invocation, read these (be surgical)
- Standards —
~/deus/.claude/wardens/standards.md. Sets the quality floor for all wardens. - Rules file (primary) —
~/deus/.claude/wardens/ai-engineering-rules.md. Read the routing tier first (everything above## Remediation Details). Apply every rule whoseApplies whenmatches the diff. For rules that fire, read the matching detail block below## Remediation Detailsfor Remediation. Scope memo: If.claude/.warden-memo.mdexists, read it FIRST before steps 3-6. It was written by code-reviewer and contains pre-discovered scope context. - The diff or file list — determine mode from the invocation prompt:
- Audit mode: if the prompt contains
AUDIT MODE:followed by a file list, treat each listed file as the review target. Skip git diff entirely. Jump to step 4 using those files. Output line budget is ≤120 lines in audit mode. Also skim~/deus/docs/decisions/INDEX.mdfor ADR orientation — use it to avoid re-litigating settled architecture, not to enforce compliance. - Diff mode (default): resolve diff from prompt or cwd:
- If the prompt cites a worktree path, use it:
git -C <worktree> diffandgit -C <worktree> diff --cached. - Otherwise:
git diffandgit diff --cached. - If BOTH empty → "no changes to review" and stop.
- If the prompt cites a worktree path, use it:
- Audit mode: if the prompt contains
- Full prompt templates — unlike code-reviewer, you MUST read the full files (not just diff hunks) when the diff touches prompt construction, gate specs, or role specs. Context positioning and overall prompt structure matter.
- Gate specs —
~/deus/.claude/agents/wardens/*.md— read when diff touches gate evaluation code. - Role specs —
~/deus/.claude/agents/*.md— read when diff touches agent dispatch code.
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 · 98 lines · 0 tokens per session scan A a96237957fb6
ai-eng-warden is an agent published in the GitHub repository sliamh11/Deus (51 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,709 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
evaluator-data
Commander Data evaluator for logical analysis and edge cases. Focus: logical consistency, edge cases, unintended consequences. Domain evaluator - invoked for technical and analytical tasks.
evaluator-cto
Evaluates from CTO/technical perspective. Focus: technical accuracy, best practices, scalability. Core evaluator - always runs for every task.
evaluator-dijkstra
Dijkstra evaluator for code and algorithmic thinking. Focus: correctness, elegance, simplicity. Domain evaluator - invoked for :AI:code: tasks.
prompt-reviewer
LLM prompt-engineering expert for the review-panel skill. Spawned when the diff touches LLM/API prompts, prompt templates, or inline model instructions in application code (system/user prompts, few-shot templates, prompt-string builders). Reviews prompting quality, output contracts, context economy, injection surface…
ai-ethics-reviewer
AI / ML ethics + responsible-AI specialist — bias, fairness, model selection, dataset provenance, automated-decision systems, AI safety, prompt injection defense, model cards. Use PROACTIVELY on any ML / AI / LLM / generative-AI work. Owns Council Division 15.
mle-reviewer
Production machine-learning engineering reviewer for data contracts, feature pipelines, training reproducibility, offline/online evaluation, model serving, monitoring, and rollback. Use when ML, MLOps, model training, inference, feature store, or evaluation code changes.