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/gosha70/code-copilot-teamWrote 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/commands/gosha70/code-copilot-team/trace)<a href="https://agentmods.dev/commands/gosha70/code-copilot-team/trace"><img src="https://agentmods.dev/badge/commands/gosha70/code-copilot-team/trace/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/commands/gosha70/code-copilot-team/trace"><img src="https://agentmods.dev/badge/commands/gosha70/code-copilot-team/trace.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.00000 | $0.00064 |
| Opus 5.5 | $0.00000 | $0.00026 |
| Sonnet 5.5 | $0.00000 | $0.00013 |
| Haiku 4.5 | $0.00000 | $0.00006 |
Grade A, and why
trace 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
Check recent LangSmith traces:
- List the 10 most recent runs from LangSmith
- Identify any runs with errors or high latency (> 30s)
- For failed runs, show the error message and which node failed
- Summarize: total runs, success rate, avg latency
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 · 6 lines · 0 tokens per session scan A d7c013cc2ae9
trace is a command published in the GitHub repository gosha70/code-copilot-team (7 stars, last pushed 17d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 64 tokens. 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-09-03.
Other commands, from other repositories
rosetta-conflicts
Surface decisions the library cannot uniquely resolve — unresolved conflicts (≥2 current records), code that contradicts an Accepted ADR, and stale records whose cited code moved on. Use to audit a decision library's health before trusting it, or when the user asks "what's contradictory / unresolved / stale in our…
fix
A code-repair command that detects and fixes errors reported by language servers, linters, or type checkers. These tools find code problems such as invalid syntax, style issues, and mismatched data types.
story-continue
Resume an interrupted story from where you left off.
local
Command "local" from getsentry/toolkit, covering examples, start the server and tail events (default), run your app with the local server auto-enabled, use a custom port and only show errors and logs (filter out transactions).
validate
Run SDLC compliance check against the current project. Validates build system, code quality, testing, CI/CD, security, documentation, VCS, and release configurations.
trace
Command "trace" from getsentry/toolkit, covering examples, list traces, list last 20 traces (default), sort by slowest first and filter by transaction name, last 24 hours.