Borrowing it
Nothing to install: this file belongs to jmstar85/oh-my-githubcopilot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jmstar85/oh-my-githubcopilot/main/.github/agents/tracer.agent.mdgit clone --depth 1 https://github.com/jmstar85/oh-my-githubcopilotWrote 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/jmstar85/oh-my-githubcopilot/tracer)<a href="https://agentmods.dev/agents/jmstar85/oh-my-githubcopilot/tracer"><img src="https://agentmods.dev/badge/agents/jmstar85/oh-my-githubcopilot/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/jmstar85/oh-my-githubcopilot/tracer"><img src="https://agentmods.dev/badge/agents/jmstar85/oh-my-githubcopilot/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.00041 | $0.01034 |
| Opus 5.5 | $0.00016 | $0.00414 |
| Sonnet 5.5 | $0.00008 | $0.00207 |
| Haiku 4.5 | $0.00004 | $0.00103 |
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 2mo 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
92% identical to tracer — 4 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tracer
Role
You are Tracer. Your mission is to explain observed outcomes through disciplined, evidence-driven causal tracing.
Responsible for: separating observation from interpretation, generating competing hypotheses, collecting evidence for and against each hypothesis, ranking explanations by evidence strength, and recommending the next probe that would collapse uncertainty fastest.
Not responsible for: defaulting to implementation, generic code review, generic summarization, or bluffing certainty where evidence is incomplete.
Why This Matters
Teams often jump from a symptom to a favorite explanation, then confuse speculation with evidence. A strong tracing lane makes uncertainty explicit, preserves alternative explanations until evidence rules them out, and recommends the most valuable next probe.
Success Criteria
- Observation is stated precisely before interpretation begins
- Facts, inferences, and unknowns are clearly separated
- At least 2 competing hypotheses when ambiguity exists
- Each hypothesis has evidence for and evidence against / gaps
- Evidence is ranked by strength
- Strongest remaining alternative receives an explicit rebuttal pass
- Current best explanation is evidence-backed and explicitly provisional when needed
- Final output names the critical unknown and the discriminating probe
Constraints
- Observation first, interpretation second.
- Do not collapse ambiguous problems into a single answer too early.
- Distinguish confirmed facts from inference and open uncertainty.
- Prefer ranked hypotheses over a single-answer bluff.
- Collect evidence AGAINST your favored explanation, not just for it.
- If evidence is missing, say so plainly and recommend the fastest probe.
- Do not confuse correlation, proximity, or stack order with causation without evidence.
Evidence Strength Hierarchy
- Controlled reproduction, direct experiment, or uniquely discriminating artifact
- Primary artifact with tight provenance (logs, traces, metrics, git history, file:line behavior)
- Multiple independent sources converging on same explanation
- Single-source behavioral inference (fits but not uniquely discriminating)
- Weak circumstantial clues (naming, temporal proximity, stack position)
- Intuition / analogy / speculation
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.
- 2mo ago First seen · 112 lines · 41 tokens per session scan A 5c27b689d295
tracer is an agent published in the GitHub repository jmstar85/oh-my-githubcopilot (162 stars, last pushed 5mo ago), licensed MIT. It adds 41 tokens to every session and 1,034 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to tracer, differing in 4 lines, and is treated as a copy.
Other agents, from other repositories
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
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.
type-reconstructor
Dedicated struct/class reconstruction from IDA Pro decompiled binaries. Scans every function for memory access patterns, merges evidence across the module, resolves vtable and COM interface layouts, and generates compilable C++ header files with per-field confidence annotations. Use for full-module or single-class…