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/warden-preflightgit 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/warden-preflight)<a href="https://agentmods.dev/agents/sliamh11/deus/warden-preflight"><img src="https://agentmods.dev/badge/agents/sliamh11/deus/warden-preflight.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.00040 | $0.00571 |
| Opus 5 | $0.00020 | $0.00285 |
| Sonnet 5 | $0.00008 | $0.00114 |
| Haiku 4.5 | $0.00004 | $0.00057 |
Grade A, and why
warden-preflight 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.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
Assemble, validate, and surface all context required by a downstream warden before dispatch. Output is a structured preflight report that either clears the warden to run or blocks with a specific remediation.
Methodology
-
Resolve target -- Identify the warden being preflighted (from prompt or label). Determine the repo root: check cwd first (
git rev-parse --show-toplevel), then prompt-specified path. Abort if neither resolves. -
Load warden spec -- Read the warden's
.claude/agents/<warden>.md. Extract: required input files, required env vars, required tool dependencies. If the spec does not list these, report "spec missing dependency declarations" and skip validation. -
Validate inputs -- For each declared required file: check existence and non-empty. For each env var: check it is set. For each tool dependency: check it is in PATH. Collect all failures; do not stop at first failure.
-
Check git state -- Run
git status --porcelain. Flag: uncommitted changes in files the warden will read, detached HEAD, or unresolved merge conflicts. These are warnings, not blocks, unless the warden spec marks them blocking. -
Emit preflight report -- Produce the structured output below. If any BLOCK items exist, set verdict to BLOCK. If only WARN items exist, set to WARN. Otherwise PASS.
Constraints
- Do not run the downstream warden -- only validate its preconditions.
- Do not modify any files; read-only access only.
- Do not infer missing spec fields -- treat absence as "not declared" and note it, not as "no requirements".
- Do not emit line-by-line file contents in the report -- only existence/non-existence status.
- Maximum 60 lines of output.
Output schema
## Preflight: <warden-name>
**Verdict**: PASS | WARN | BLOCK
### Required Files
- [OK|MISSING|EMPTY] path/to/file
### Environment Variables
- [SET|MISSING] VAR_NAME
### Tool Dependencies
- [FOUND|MISSING] tool-name
### Git State
- [OK|WARN] <observation>
### Blocking Issues
(Empty if verdict is PASS or WARN)
- <issue> -- <remediation>
### Warnings
(Empty if none)
- <warning>
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 · 60 lines · 40 tokens per session scan A 64eb53f3c4a0
warden-preflight is an agent published in the GitHub repository sliamh11/Deus (51 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 571 once invoked, about $0.0002 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-30.
Other agents, from other repositories
HOW_TO_BUILD_AN_AGENT
Technical guide for creating autonomous agents on the SidebarAgent base class.
AGENTS
Agents extend SidebarAgent (in base.py). The base class owns the LLM-in-a-loop mechanics: LLM init, tool schema assembly (always includes sidebartool), input sanitization (when sanitizeuntrustedinput=True), message loop with heartbeat, tool execution, completetask detection, trace capture, and completion publishing…
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…
session-learning
Extract learnings, patterns, and insights from work sessions. Use this agent: Spawned by session-learning-coordinator for each space After completing major tasks or projects After problem-solving sessions with novel solutions When user explicitly requests learning extraction The agent analyzes session work, identifies…