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 skills add allemaar/open-skills --skill plan-cleanupgit clone --depth 1 https://github.com/allemaar/open-skillsWrote 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/skills/allemaar/open-skills/plan-cleanup)<a href="https://agentmods.dev/skills/allemaar/open-skills/plan-cleanup"><img src="https://agentmods.dev/badge/skills/allemaar/open-skills/plan-cleanup/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/skills/allemaar/open-skills/plan-cleanup"><img src="https://agentmods.dev/badge/skills/allemaar/open-skills/plan-cleanup.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.00074 | $0.00939 |
| Opus 5 | $0.00037 | $0.00469 |
| Sonnet 5 | $0.00015 | $0.00188 |
| Haiku 4.5 | $0.00007 | $0.00094 |
Grade A, and why
plan-cleanup 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/plan-cleanup
Remove planning artifacts and tech debt after a plan has been executed. No new work. No scope additions. Just cleanup.
Structured execution spec:
protocol.yon. Read it for the canonical rules and step sequence; this file is explanation. The two must stay in sync — if you edit one, update the other and refresh the@STAMPdate.
Phase 1 — Identify Artifacts
Scan for artifacts left behind by the planning and execution cycle:
Planning docs (created by /plan-create, /plan-phases, /plan-deep-dive):
PLAN.mdimplementation_plan.mdtask.md(if created as a plan artifact, not a pre-existing project file)- Any
*-plan.mdfiles in the project root
Execution scaffolding (created by /plan-execute or setup steps):
- Temp files, stub files, or files explicitly marked as temporary in the plan
- Any file whose sole purpose was to scaffold or support the plan run
Tool artifacts:
.claude/directories created incidentally in skill or tool folders (not the user's project.claude/)
For each candidate, verify: is this file needed by the project going forward? If yes, leave it. If it exists only because of the planning cycle, it's an artifact.
Gate: list every artifact found before removing anything. If none found, declare "No artifacts found — workspace is clean" and stop.
Phase 2 — Confirm and Remove
Present the artifact list to the user:
"Found the following planning artifacts:
- [file 1]
- [file 2]
Remove all? (y / skip [filename] / cancel)"
On confirmation:
- Remove each confirmed artifact
- For git repos: use
git rmif the file is tracked,rmif untracked - Never remove files outside the current project scope
Gate: do not remove any file not explicitly identified in Phase 1. Do not remove files the user skipped.
Phase 3 — Verify and Commit
- Confirm each artifact is gone — list what was removed.
- If in a git repo and files were tracked: commit with message
chore: remove planning artifacts. - Push if the user's workflow includes pushing (check if prior commits in this session were pushed).
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 96 lines · 74 tokens per session scan A 8737644d8a01
plan-cleanup is a skill published in the GitHub repository allemaar/open-skills (14 stars, last pushed 24d ago), licensed Apache-2.0. It adds 74 tokens to every session and 939 once invoked, about $0.0004 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
polis-protocol
Set up and run a self-improving, multi-vendor AI agent team with the Polis Protocol — a markdown polis/ folder where each agent is a citizen with a capability card, tasks are contracts routed to whoever has the best track record by a learning router, settled work files lessons that compound into team memory, and…
media
Skill "media" from ymxlx/polis-protocol, covering polis protocol: a self-optimizing city of agents, the core idea, when this skill is active, structure of a polis and the first thing to do every session.
_data
Skill "_data" from ymxlx/polis-protocol, covering polis protocol: a self-optimizing city of agents, the core idea, when this skill is active, structure of a polis and the first thing to do every session.
subagent-driven-development
Execute plans via delegatetask subagents (2-stage review).
mcporter
List, auth, and call MCP servers/tools from the terminal.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.