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/SlashyIsTaken/fp-pluginplazaWrote 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/slashyistaken/fp-pluginplaza/strip)<a href="https://agentmods.dev/commands/slashyistaken/fp-pluginplaza/strip"><img src="https://agentmods.dev/badge/commands/slashyistaken/fp-pluginplaza/strip/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/slashyistaken/fp-pluginplaza/strip"><img src="https://agentmods.dev/badge/commands/slashyistaken/fp-pluginplaza/strip.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.00015 | $0.00392 |
| Opus 5 | $0.00008 | $0.00196 |
| Sonnet 5 | $0.00003 | $0.00078 |
| Haiku 4.5 | $0.00002 | $0.00039 |
Grade A, and why
strip 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 9d 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
This is the task-based stripper, not the always-on prior: a deliberate cleanup pass you asked for. Apply the fp-minify doctrine to the target and remove or compress comments that don't earn their place.
Target: $ARGUMENTS — if empty, the file or block currently in focus. If that's unclear, ask which before touching anything.
Rules (the same the /fp-minify skill uses):
- Keep comments that carry a non-obvious why, or meaning a name can't hold (config values, magic numbers, units, ranges, invariants, constraints).
- Keep API doc comments — JSDoc/TSDoc, docstrings, godoc — they're caller contracts.
- Cut or shorten comments that restate what the code plainly does, narrate the happy path, or tell a story that belongs in a commit, PR, or ticket. Compress an earned-but-bloated comment to one self-contained line, splitting it into separate one-liners at their own anchors if one line can't hold it.
- Collapse the multi-line blocks. Measurements, sample counts, rejected alternatives, and what broke last time are not reasons to keep a paragraph. Keep the rule, drop the road to it.
- Thin them out. Where nearly every stanza carries a comment, most of them aren't earning their place. Count matters as much as length.
- Change comments only. Never alter what the code does.
Before deleting a lot at once, show the user what you'll remove and let them hold parts back. When unsure whether a comment is earned, shorten it rather than drop it.
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.
- 9d ago First seen · 33 lines · 15 tokens per session scan A 0e66c1a250ad
strip is a command published in the GitHub repository SlashyIsTaken/fp-pluginplaza (2 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 392 once invoked, about $0.0001 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-31.
Other commands, from other repositories
conjure-config
Set, view, or remove conjure preferences. Asks questions to understand what you want, then writes plain-language instructions that conjure commands follow automatically.
conjure-agent
Creates or updates a Claude Code agent definition (/.claude/agents/ .md or project-local).
conjure
Use when you want to build a new Claude Code skill, agent, hook, or MCP server but aren't sure which — or when you want to describe what you want in plain language. Auto-detects the right artifact type, asks targeted questions, explains the reasoning, then builds it.
conjure-help
Show help for the conjure toolkit — all commands, argument syntax, update modes, and decision guide. Use when you want to know which conjure command to use or how any conjure command works.
conjure-mcp
Create a Claude Code MCP (Model Context Protocol) server. Provide a description of what external system or data source you want Claude to connect to.
web-design
Design and build a complete website or webapp from a project brief — end-to-end workflow from design to working React/Vite code.