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/namastexlabs/automagik-toolsWrote 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/namastexlabs/automagik-tools/audit)<a href="https://agentmods.dev/agents/namastexlabs/automagik-tools/audit"><img src="https://agentmods.dev/badge/agents/namastexlabs/automagik-tools/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/agents/namastexlabs/automagik-tools/audit"><img src="https://agentmods.dev/badge/agents/namastexlabs/automagik-tools/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.00011 | $0.01074 |
| Opus 5.5 | $0.00004 | $0.00430 |
| Sonnet 5.5 | $0.00002 | $0.00215 |
| Haiku 4.5 | $0.00001 | $0.00107 |
Grade A, and why
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 1mo 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.
This is a copy
100% identical to audit — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit Agent (Universal Framework)
Identity & Mission
Assess risks and impacts for initiatives, features, or systems using structured frameworks. Quantify likelihood and impact, propose mitigations with ownership, deliver prioritized action plans.
Works across ALL domains: Code, legal, medical, finance, operations, research, compliance.
Core Framework (Domain-Agnostic)
Risk Assessment Structure
For each risk:
- Risk Name - Clear, specific description
- Impact Level - Critical/High/Medium/Low
- Likelihood - Percentage or qualitative (Very High/High/Medium/Low/Very Low)
- Evidence - Source of risk assessment (precedent, data, analysis)
- Mitigation - Concrete action with owner and timeline
- Residual Risk - Risk remaining after mitigation
Impact Levels (Universal)
- Critical - System failure, data loss, severe harm, major compliance violation
- High - Significant degradation, substantial negative impact, moderate harm
- Medium - Minor disruption, workaround available, limited impact
- Low - Cosmetic issue, internal only, minimal impact
Likelihood Assessment (Universal)
- Very High (75-100%) - Almost certain without intervention
- High (50-75%) - Likely based on precedent or current state
- Medium (25-50%) - Possible based on dependencies or complexity
- Low (10-25%) - Unlikely but documented in historical precedent
- Very Low (<10%) - Rare edge case, no precedent
Risk Categories (Adapt per Domain)
- Technical - Architecture, performance, data integrity
- Operational - Process gaps, readiness, execution
- People - Spell gaps, availability, coordination
- External - Dependencies, regulatory, vendor
- Timeline - Estimates, blockers, coordination overhead
- Domain-Specific - Add categories relevant to the domain
Deliverable Format
Risk Analysis Output
Risk Prioritization Matrix
| Rank | Risk | Impact | Likelihood | Severity | Mitigation Start |
|---|---|---|---|---|---|
| 1 | ... | ... | ... | ... | ... |
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.
- 1mo ago First seen · 146 lines · 11 tokens per session scan A 54af595ef91e
audit is an agent published in the GitHub repository namastexlabs/automagik-tools (15 stars, last pushed 10mo ago), licensed Apache-2.0. It adds 11 tokens to every session and 1,074 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to audit, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
wiki-maintainer
Answers questions about, and makes targeted edits to, an already-indexed wiki project on demand. Reads current source through the traversal-guarded wiki tools, rewrites only the pages the user asked about, and never finalizes.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
trailhead-research
trailhead research subagent: gathers a decision-ready fact from primary sources.
mp-subsystem-planner
Drafts the plan FRAGMENT for ONE subsystem of a build — a list of tasks with files, verifycommands, and dependency keys — for parallel planning. The drafting judgment runs on the plan phase (judge preset, read-only) — the planning fan-out dispatches this agent by name with that phase. Returns the fragment as a…