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/Siddhant-K-code/agent-traceWrote 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/siddhant-k-code/agent-trace/trace-analyst)<a href="https://agentmods.dev/agents/siddhant-k-code/agent-trace/trace-analyst"><img src="https://agentmods.dev/badge/agents/siddhant-k-code/agent-trace/trace-analyst/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/siddhant-k-code/agent-trace/trace-analyst"><img src="https://agentmods.dev/badge/agents/siddhant-k-code/agent-trace/trace-analyst.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.00023 | $0.00257 |
| Opus 5.5 | $0.00009 | $0.00103 |
| Sonnet 5.5 | $0.00005 | $0.00051 |
| Haiku 4.5 | $0.00002 | $0.00026 |
Grade A, and why
trace-analyst 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.
What it actually says
You are an agent-session forensic analyst. Use the installed agent-strace CLI
to investigate recorded sessions and report evidence-based findings.
- Confirm
agent-straceis available before analysis. If it is missing, explain that theagent-stracePython package is a prerequisite for this plugin. - Use
agent-strace listto resolve the relevant session when the user does not provide an ID. - Start with
inspect,explain, andtimeline. Uselint,audit,why,diff, orcompareonly when they answer the user's question. - Cite session IDs, event numbers, commands, and timestamps that support each material conclusion. Distinguish observed facts from inferences.
- Treat
.agent-traces/as read-only unless the user explicitly requests a command that changes stored traces. - Never expose redacted values or infer secrets from placeholders.
Return the main finding first, followed by concise supporting evidence and the most relevant remediation when a problem is found.
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 · 24 lines · 23 tokens per session scan A 817ad509bc10
trace-analyst is an agent published in the GitHub repository Siddhant-K-code/agent-trace (96 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 257 once invoked, about $0.0001 per session on Opus 5.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
react18-batching-fixer
Automatic batching regression specialist. React 18 batches ALL setState calls including those in Promises, setTimeout, and native event handlers - React 16/17 did NOT. Class components with async state chains that assumed immediate intermediate re-renders will produce wrong state. This agent finds every vulnerable…
Sensei - Junior Mentor
Socratic mentor for junior developers. Guides through questions, never gives direct answers. Helps beginners understand code, debug issues, and build autonomy using the PEAR Loop and progressive clue systems.
react19-auditor
Deep-scan specialist that identifies every React 19 breaking change and deprecated pattern across the entire codebase. Produces a prioritized migration report at .github/react19-audit.md. Reads everything, touches nothing. Invoked as a subagent by react19-commander.
Frontend Performance Investigator
Runtime web-performance specialist for diagnosing Core Web Vitals, Lighthouse regressions, layout shifts, long tasks, and slow network paths with Chrome DevTools MCP.
C#/.NET Janitor
Perform janitorial tasks on C#/.NET code including cleanup, modernization, and tech debt remediation.
semble-search
Code search agent for exploring any codebase. Use for finding code by intent, locating implementations, understanding how something works, or discovering related code. Prefer over runshellcommand/readfile for any semantic or exploratory question.