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/akougkas/wtf-pWrote 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/akougkas/wtf-p/remove-section)<a href="https://agentmods.dev/commands/akougkas/wtf-p/remove-section"><img src="https://agentmods.dev/badge/commands/akougkas/wtf-p/remove-section/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/akougkas/wtf-p/remove-section"><img src="https://agentmods.dev/badge/commands/akougkas/wtf-p/remove-section.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.00012 | $0.00119 |
| Opus 5.5 | $0.00005 | $0.00048 |
| Sonnet 5.5 | $0.00002 | $0.00024 |
| Haiku 4.5 | $0.00001 | $0.00012 |
Grade A, and why
remove-section 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 29d 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.
This is a copy
86% identical to wtfp:remove-section — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
WTFP_ACTION_UNAVAILABLE
Action: remove-section
Target: claude
Unavailable capabilities: filesystem.delete
Unavailable effects: filesystem.delete
No workflow, tool, network request, package operation, external issue, VCS operation, or other effect ran. Safe alternative: preserve project state and return a manual, non-executed handoff for the requested operation.
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.
- 29d ago Changed 7589943812d0
- 1mo ago First seen · 17 lines · 12 tokens per session scan A 54a3a48fbde3
remove-section is a command published in the GitHub repository akougkas/wtf-p (20 stars, last pushed 11d ago), licensed MIT. It adds 12 tokens to every session and 119 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to wtfp:remove-section, differing in 3 lines, and is treated as a copy.
Other commands, from other repositories
status
Display project status, active tracks, and next actions.
continue
Detects current wave progress for a feature and resumes at the next step. Scans docs/feature/ for artifacts.
dashboard-session-fork
Fork a session into a new one. Usage /dashboard:session-fork.
dashboard-session-hide
Hide a session from the dashboard list. Usage /dashboard:session-hide.
repo-architect
Repository structure optimization and multi-repo management with ruv-swarm coordination for scalable project architecture and development workflows.
project-stage-detect
Detect project phase and recommend actions.