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 skills add budagov-lab/DreamTeam --skill auditor-system-auditgit 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/skills/budagov-lab/dreamteam/auditor-system-audit)<a href="https://agentmods.dev/skills/budagov-lab/dreamteam/auditor-system-audit"><img src="https://agentmods.dev/badge/skills/budagov-lab/dreamteam/auditor-system-audit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/budagov-lab/dreamteam/auditor-system-audit"><img src="https://agentmods.dev/badge/skills/budagov-lab/dreamteam/auditor-system-audit.svg" alt="Reviewed on agentmods" width="80" 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.00037 | $0.00328 |
| Opus 5 | $0.00018 | $0.00164 |
| Sonnet 5 | $0.00007 | $0.00066 |
| Haiku 4.5 | $0.00004 | $0.00033 |
Grade A, and why
auditor-system-audit 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 9d 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.
What it actually says
Auditor System Audit
When to Use
- When
python -m dreamteam update-task <id> doneprintsTRIGGER_AUDITOR(source of truth) - After every 200 completed tasks
- When duplicate code or circular dependencies are suspected
Workflow
- Read from DB: Terminal →
python -m dreamteam memory-get architecture,python -m dreamteam scheduler --list(or MCP dreamteam_*) - Scan codebase: Modules, functions, dependencies (read source files)
- Check: Duplicate functions, circular dependencies, layer violations
- Report: List issues with severity
- Create tasks: Refactor tasks for each critical issue
- Write architecture: Draft →
.dreamteam/temp/, thenpython -m dreamteam memory-set architecture <file>. DB only.
Checks
- Duplicate functions across modules
- Circular dependencies in DAG or code
- Layer violations (e.g. UI depending on DB directly)
- Orphaned or dead code
Output
- Audit report (markdown)
- Refactor tasks for critical issues
- Architecture: Write draft to
.dreamteam/temp/architecture_new.md, then Terminal →python -m dreamteam memory-set architecture <file>. Do NOT write to.dreamteam/memory/architecture.mddirectly — DB only.
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.
- 9d ago First seen · 35 lines · 37 tokens per session scan A 2197609b814b
auditor-system-audit is a skill published in the GitHub repository budagov-lab/DreamTeam (1 stars, last pushed 5mo ago), licensed MIT. It adds 37 tokens to every session and 328 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 skills, from other repositories
doubt-driven-development
Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when you want every assumption cross-examined before proceeding, when stress-testing a plan for hidden failure modes, when correctness matters more than speed, when working in unfamiliar code, when stakes are high…
trace
Use when encountering bugs, test failures, runtime errors, broken builds, or "this doesn't work" reports. Systematic root-cause analysis before any patch — never blind-patches symptoms. Standalone, ends with a final-integration review of the fix. Trigger with /hyperflow:trace, "debug this", "find the root cause", "why…
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
issue-root-resolution
Trigger: root audit, atacar la raíz, issue roots, backlog roots, mechanism map, deletion-driven fix, resolver issues de raíz, close outdated issues. Audit and resolve issue clusters by verified root cause.
issue
Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…
review-loop
Run the adversarial verification loop — implement, then hand the change to a fresh checker that did not write it, fix what it finds, and re-dispatch until APPROVE. Use before claiming any behavioural change is done, and on requests like "review loop", "adversarial review", "independent review", "get this verified"…