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 skills/siddhant-k-code/agent-trace/agent-stracenpx skills add Siddhant-K-code/agent-trace --skill agent-stracegit clone --depth 1 https://github.com/Siddhant-K-code/agent-traceWhat 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.00054 | $0.00402 |
| Opus 5 | $0.00027 | $0.00201 |
| Sonnet 5 | $0.00011 | $0.00080 |
| Haiku 4.5 | $0.00005 | $0.00040 |
Grade A, and why
agent-strace 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 3d 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
agent-strace
Use the local agent-strace executable. The plugin contributes lifecycle hooks,
but the Python package must also be installed and available on PATH.
Prerequisite check
Run agent-strace --version. If it is unavailable, stop and provide one of:
uv tool install agent-strace
pip install agent-strace
Do not silently substitute another tracing tool.
Capture
Installed plugin hooks automatically record new Copilot CLI sessions to
.agent-traces/. Do not also run agent-strace setup --cli copilot; that would
register duplicate hooks.
Investigate
Choose the smallest command set that answers the request:
agent-strace list
agent-strace inspect <session-id>
agent-strace replay <session-id>
agent-strace explain <session-id>
agent-strace timeline <session-id>
agent-strace why <session-id> <event-number>
agent-strace lint <session-id>
agent-strace audit <session-id>
agent-strace cost <session-id>
agent-strace diff <session-a> <session-b>
agent-strace compare <session-a> <session-b>
Resolve an omitted session ID with agent-strace list. Prefer text output for
interactive analysis and JSON only when structured processing is necessary.
Report exact session IDs and event numbers for material findings.
Safety
- Treat trace storage as read-only unless the user requests retention, import, anonymization, or another mutating operation.
- Preserve secret redaction.
- Do not claim causal intent from proximity alone; use
whyor clearly label the conclusion as an inference.
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.
- 3d ago First seen · 57 lines · 54 tokens per session scan A 2fb5b3651d9d
agent-strace is a skill published in the GitHub repository Siddhant-K-code/agent-trace (90 stars, last pushed 11d ago), licensed MIT. It adds 54 tokens to every session and 402 once invoked, about $0.0003 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 skills, from other repositories
project-graveyard
Scans the developer's machine for dead side projects, autopsies each one from its git history (died at the payments wall, killed by a newer project, finished but never shipped), surfaces their personal death patterns, and picks the corpse most worth resurrecting — then helps ship it. Use when the user mentions…
web-app-penetration-testing
Pentest a web app or website end to end — black-box testing of a live URL, staging environment, or local dev server that finds and exploits real vulnerabilities (auth bypass, broken access control, IDOR, injection, XSS, SSRF, business logic) and proves each one with a working proof-of-concept instead of a signature…
haiku
When writing a haiku for this bot, follow these conventions.
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…