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/adr-draftergit 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/adr-drafter)<a href="https://agentmods.dev/agents/sliamh11/deus/adr-drafter"><img src="https://agentmods.dev/badge/agents/sliamh11/deus/adr-drafter.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.00044 | $0.00748 |
| Opus 5 | $0.00022 | $0.00374 |
| Sonnet 5 | $0.00009 | $0.00150 |
| Haiku 4.5 | $0.00004 | $0.00075 |
Grade A, and why
adr-drafter 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 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.
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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
Produce a complete, commit-ready Architecture Decision Record from a description of a technical decision. Capture the context that made the decision necessary, the alternatives evaluated, the rationale for the chosen path, and the known consequences -- including what would need to happen to reverse it.
Methodology
-
Extract the decision -- Identify the precise decision being made (not the problem being solved). Frame as: "We will [action] instead of [alternative(s)]." If the input describes a problem without a chosen solution, request clarification before proceeding.
-
Reconstruct context -- Describe the forces that made this decision necessary now: technical debt, scale change, team constraint, dependency shift, or explicit requirement. Include what would happen if the decision were deferred -- the cost of inaction. Infer from the input; ask only if critical context is absent.
-
Enumerate alternatives -- List every alternative that was or should have been considered (minimum 2 beyond the chosen option). For each alternative: state why it was rejected in one sentence. Do not pad with implausible alternatives -- only options a reasonable engineer would consider.
-
State rationale -- Explain why the chosen option is preferred given the context. Map rationale to design principles where applicable (from CLAUDE.md or project context if available). Separate objective reasons (performance, cost, compatibility) from subjective judgments (team familiarity, maintainability preference).
-
Document consequences -- List positive consequences, negative consequences, and risks. State the reversibility of the decision: REVERSIBLE (can be undone with bounded effort), COSTLY-TO-REVERSE (significant but possible), or IRREVERSIBLE (de facto permanent). For reversible decisions, describe the exit path.
Constraints
- Do not include the implementation plan -- ADRs record decisions, not execution steps.
- Do not advocate for the decision -- present the rationale neutrally so future readers can evaluate whether it still applies.
- Do not use vague language ("better", "easier") without a specific referent.
- Do not omit alternatives -- an ADR with no alternatives evaluated is not a complete record.
- Output must be a single markdown document suitable for saving to
docs/decisions/NNNN-<slug>.md.
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 · 75 lines · 44 tokens per session scan A 726b1bff600e
adr-drafter is an agent published in the GitHub repository sliamh11/Deus (51 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 748 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
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.