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 commands/athola/skrills/skill-trace-disablegit clone --depth 1 https://github.com/athola/skrillsWrote 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/athola/skrills/skill-trace-disable)<a href="https://agentmods.dev/commands/athola/skrills/skill-trace-disable"><img src="https://agentmods.dev/badge/commands/athola/skrills/skill-trace-disable.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.1 | $0.00008 | $0.00214 |
| Opus 5 | $0.00004 | $0.00107 |
| Sonnet 5 | $0.00002 | $0.00043 |
| Haiku 4.5 | $0.00001 | $0.00021 |
Grade A, and why
skill-trace-disable 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 6d 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
Skill Trace Disable
Disable skill tracing using the skrills MCP server.
Use the mcp__plugin_skrills_skrills__disable-skill-trace tool with:
target: claude, codex, or both (default: both)dry_run: Preview without changes
Parse $ARGUMENTS for:
--target <target>or-t <target>: Target CLI (default: both)--dry-runor-n: Preview mode
Report:
- Skills de-instrumented
- Backup files removed (if any)
- Confirmation tracing is disabled
Handle errors:
- If target invalid: List valid options (claude, codex, both)
- If tracing not enabled: Report current state, no action needed
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.
- 6d ago First seen · 27 lines · 8 tokens per session scan A e24a349138a6
skill-trace-disable is a command published in the GitHub repository athola/skrills (69 stars, last pushed yesterday), licensed MIT. It adds 8 tokens to every session and 214 once invoked, about $0.0000 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 commands, from other repositories
project
Manage projects: register repos, inspect, configure per-project settings, and remove.
send
Send a message to a running agent session. Use this to correct or direct a live agent mid-stream without killing and respawning it.
ship-an-mcp-server
Workflow recipe — make your product agent-usable by chaining 4 skills, spec to pricing.
rescue-an-account
Workflow recipe — diagnose an at-risk customer and build the full save play through to renewal by chaining 4 skills.
prompt-optimizer
Analyze and rewrite a prompt to maximize clarity, specificity, and output quality.
checklist
Generate a custom checklist for the current feature based on user requirements.