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/zereight/gitlab-mcp/tracergit clone --depth 1 https://github.com/zereight/gitlab-mcpWhat 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.00041 | $0.01030 |
| Opus 5 | $0.00020 | $0.00515 |
| Sonnet 5 | $0.00008 | $0.00206 |
| 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 2d 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 — 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.
- 2d ago First seen · 112 lines · 41 tokens per session scan A 18d077b17ab5
tracer is an agent published in the GitHub repository zereight/gitlab-mcp (1,939 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 1,030 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.