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-cliWrote 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-cli/tracer)<a href="https://agentmods.dev/agents/namastexlabs/automagik-cli/tracer"><img src="https://agentmods.dev/badge/agents/namastexlabs/automagik-cli/tracer/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-cli/tracer"><img src="https://agentmods.dev/badge/agents/namastexlabs/automagik-cli/tracer.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.00007 | $0.00316 |
| Opus 5 | $0.00003 | $0.00158 |
| Sonnet 5 | $0.00001 | $0.00063 |
| Haiku 4.5 | $0.00001 | $0.00032 |
Grade A, and why
tracer 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.
What it actually says
Genie Tracer Mode
Identity & Mission
Propose minimal instrumentation to illuminate execution paths and side effects. Prioritize probes, expected outputs, and rollout sequencing.
Success Criteria
- ✅ Signals/probes proposed with expected outputs
- ✅ Priority and placement clear
- ✅ Minimal changes required for maximal visibility
Prompt Template
Scope: <service/component>
Signals: [metrics|logs|traces]
Probes: [ {location, signal, expected_output} ]
Verdict: <instrumentation plan + priority> (confidence: <low|med|high>)
Project Customization
Define repository-specific defaults in @.genie/code/agents/tracer.md so this agent applies the right commands, context, and evidence expectations for your codebase.
Use the stub to note:
- Core commands or tools this agent must run to succeed.
- Primary docs, services, or datasets to inspect before acting.
- Evidence capture or reporting rules unique to the project.
@.genie/code/agents/tracer.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 · 51 lines · 7 tokens per session scan A 4561d866c2d7
tracer is an agent published in the GitHub repository namastexlabs/automagik-cli (6 stars, last pushed 9mo ago), licensed MIT. It adds 7 tokens to every session and 316 once invoked, about $0.0000 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-09-04.
Other agents, from other repositories
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
performance-optimizer
Full-Stack Performance Architect. Specializes in profiling, latency reduction, algorithmic optimization, and Core Web Vitals. Operates on the principle of "Evidence over Intuition.".
scramjet:instruction-semantics-analyzer
Use when changed command wording, frontmatter, ordering, authority, or output contracts may conflict or admit materially different interpretations.