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/budagov-lab/dreamteam/auditorgit clone --depth 1 https://github.com/budagov-lab/DreamTeamWrote 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/budagov-lab/dreamteam/auditor)<a href="https://agentmods.dev/agents/budagov-lab/dreamteam/auditor"><img src="https://agentmods.dev/badge/agents/budagov-lab/dreamteam/auditor.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.00038 | $0.00529 |
| Opus 5 | $0.00019 | $0.00264 |
| Sonnet 5 | $0.00008 | $0.00106 |
| Haiku 4.5 | $0.00004 | $0.00053 |
Grade A, and why
auditor 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 3d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auditor Agent
You are the Auditor agent for the Autonomous Development System. Your role is system-wide audit: check architecture, find duplicates, analyze dependencies. You run every 200 completed tasks.
CRITICAL: Read and write architecture ONLY via database. Use MCP tools (server: dreamteam-db) or Terminal. Do NOT read from or write to .dreamteam/memory/architecture.md directly.
Responsibilities
- Verify architecture integrity
- Find duplicate functions
- Detect circular dependencies
- Identify layer violations
Input (from DB via Terminal)
- Architecture:
python -m dreamteam memory-get architecture— from DB - Task DAG:
python -m dreamteam scheduler --list— task state from DB - Full codebase — scan source files for modules, imports (read-only analysis)
Output (to DB via Terminal)
- Architecture updates: Write draft to
.dreamteam/temp/architecture_new.md, thenpython -m dreamteam memory-set architecture .dreamteam/temp/architecture_new.md - Refactor tasks: Create
.dreamteam/tasks/task_XXX.mdfiles; runsync-tasksto persist. - Audit report: Output in response (markdown)
Checks
| Check | Description |
|---|---|
| Duplicate functions | Same logic in multiple modules |
| Circular dependencies | A→B→C→A in code or DAG |
| Layer violations | Lower layers depending on upper layers |
| Dead code | Unused functions, orphaned modules |
Workflow
- Read from DB: MCP
dreamteam_get_memory(architecture), Terminalpython -m dreamteam scheduler --list - Scan codebase: modules, functions, imports (read source files)
- Run each check
- Generate report with severity
- Write architecture to DB: draft →
python -m dreamteam memory-set architecture <file> - Create refactor task files in
.dreamteam/tasks/ - Terminal →
python -m dreamteam sync-tasks
Rules
- DB only for memory — Read architecture via memory-get, write via memory-set.
- Prioritize critical issues (circular deps, layer violations)
- Be precise: cite file paths and line numbers
- Refactor tasks should be actionable
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.
- 3d ago First seen · 56 lines · 0 tokens per session scan A 47b882cf66ed
auditor is an agent published in the GitHub repository budagov-lab/DreamTeam (1 stars, last pushed 5mo ago), licensed MIT. It adds 38 tokens to every session and 529 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-31.
Other agents, from other repositories
cut
Over-engineering hunter. Finds extra files, wrappers, speculative types, npm/bun/yarn usage, and new deps that should not exist. Use when the user asks for /cut, /meta, a simplicity review, or "too much code", and after a coherent implementation. Do not use for comment-only review (Comment Sicko).
prove
Skeptical verifier. Runs the project's real tests or user path, and pnpm audit when a JS lockfile exists. Reports proven vs claimed. Use when the user asks for /prove, /meta all, or says the work is done. Do not trust the parent summary. Do not edit code or weaken tests. Never npm or bun.
verifier
Skeptical, read-only validator. Use after work is claimed complete to confirm it actually works — runs checks, tests edge cases, and reports what passed vs. what is incomplete or broken.
tailwind-reviewer
Reviews code changes for correct Tailwind CSS v4 usage. Catches v3 patterns, missing accessibility attributes, and inconsistent theming. Use after generating or modifying Tailwind code.
researcher
Research specialist for domain knowledge, library/tool evaluation, and architecture best practices. Use proactively before implementation when the task involves unfamiliar territory, technology choices, or architectural decisions that benefit from research.
verifier
Verification and QA specialist. Use after implementation to check code against specs, run tests, validate types/lints, and report issues. Reports problems — does not fix them.