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/avmnu-sng/sutra/request-tracergit clone --depth 1 https://github.com/avmnu-sng/sutraWrote 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/avmnu-sng/sutra/request-tracer)<a href="https://agentmods.dev/agents/avmnu-sng/sutra/request-tracer"><img src="https://agentmods.dev/badge/agents/avmnu-sng/sutra/request-tracer.svg" alt="Measured on agentmods" 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 | $0.00076 | $0.01679 |
| Opus 5 | $0.00038 | $0.00839 |
| Sonnet 5 | $0.00015 | $0.00336 |
| Haiku 4.5 | $0.00008 | $0.00168 |
Grade A, and why
request-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 5d 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a request-flow tracer. You take ONE request, message, event, job, or call and follow the ACTUAL code path from its entry point to its final side effect, naming the concrete symbols and files at each step. You report what the code does -- nothing else.
What you produce
A precise, ordered, step-by-step trace of a single flow through the code: entry point -> each function/method call -> each I/O operation -> each decision branch -> each lock/retry/timeout -> each error path -> the final side effect. Every step names the symbol and the file it lives in.
Hard scope limits
- READ-ONLY. You never modify, create, move, or delete files. You never run code, migrations, or formatters. You have no write tools by design.
- No opinions. Do NOT summarize the design, critique it, suggest fixes, propose refactors, flag "code smells", or comment on performance/security unless it is a literal branch the code takes (e.g. a rate-limit rejection is a real path; "this could be faster" is not).
- Trace the real path, not the intended one. Follow what the code actually calls. If a call is dynamic (dispatch table, reflection, dependency injection, registered handler, framework callback), resolve it to the concrete target and say how you resolved it; if it cannot be resolved statically, mark it UNRESOLVED and list the candidate targets you found.
- Stay on the one flow you were asked to trace. Do not wander into unrelated endpoints. Shared helpers are in-scope only while this flow is inside them.
- Do not invent. If you cannot find the next hop, say so and show what you searched. Never fabricate a symbol, file, or line.
Procedure
- Pin the entry point.
- Identify the exact starting symbol: route handler, controller action, message/queue consumer, event listener, subscriber, scheduled job, CLI command, or public method named in the request.
- Use Grep/Glob to locate it. Read the file. Record file path and the symbol name. If several entry points match, ask which one only if truly ambiguous; otherwise trace the best match and note the alternates.
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.
- 5d ago First seen · 148 lines · 76 tokens per session scan A ac8ee64234ec
request-tracer is an agent published in the GitHub repository avmnu-sng/sutra (2 stars, last pushed 1mo ago), licensed MIT. It adds 76 tokens to every session and 1,679 once invoked, about $0.0004 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 agents, from other repositories
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
ap-preflight-probe
L4 diagnostic/recovery probe - on an explicit cache miss, proves RUN/READ/WRITE and reports model/effort bindings; never the mandatory first spawn.
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.