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 aiocean/claude-plugins --skill aio-perfectizegit clone --depth 1 https://github.com/aiocean/claude-pluginsWrote 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/aiocean/claude-plugins/aio-perfectize)<a href="https://agentmods.dev/skills/aiocean/claude-plugins/aio-perfectize"><img src="https://agentmods.dev/badge/skills/aiocean/claude-plugins/aio-perfectize/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/aiocean/claude-plugins/aio-perfectize"><img src="https://agentmods.dev/badge/skills/aiocean/claude-plugins/aio-perfectize.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.00099 | $0.00806 |
| Opus 5.5 | $0.00040 | $0.00322 |
| Sonnet 5.5 | $0.00020 | $0.00161 |
| Haiku 4.5 | $0.00010 | $0.00081 |
Grade A, and why
aio-perfectize 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 yesterday.
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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Perfectize
Overview
Perfect here is a verified fixed point: no further change survives checking against the bar. The pass edits work that already passes its own checks, keeps everything the author fixed in place, and reports what it changed and what it could not verify. It never calls the result perfect.
Freeze first
Before the first edit, write the frozen core in your reply and snapshot the
incumbent (a cp or a git commit) so any edit can be reverted:
- requirements, in the user's words
- public interface: exports, signatures, file formats, headings others link to
- behavior pinned by existing tests; the tests themselves are frozen
- facts and numbers
- the author's voice: the distinctive phrases and rhythm that make it theirs
- scope: only the files or sections the user named
Pass
- Remove first. List every element that can go without changing the frozen core: dead code, duplicated logic, unused parameters, repeated or hedging sentences, orphan steps. Remove those. Describe this to yourself as editing and removing, not improving.
- One named gap per edit. Every further change is one small edit that names the observable gap it closes: a failing check, a measurable size or speed, a requirement not yet shown. No named gap, no edit.
- Accept or revert. Run the checks for the type (tests, build, type check, link check, recomputed numbers). Keep the edit only if every earlier-passing check still passes and the frozen core is unchanged; otherwise revert it. If only taste can decide, have a fresh-context subagent compare the two versions blind, in both orders; a split or a tie keeps the incumbent. With no subagent, make only the changes a check or the frozen core decides.
- Raise the bar. After a cycle, compare the result with one exemplar (the user's, the project's own best, or a canonical work) and turn each observable gap into the next cycle's named gaps. Stop after two consecutive cycles that accept nothing, or after three cycles.
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.
- yesterday First seen · 77 lines · 99 tokens per session scan A 5a39d12979b9
aio-perfectize is a skill published in the GitHub repository aiocean/claude-plugins (4 stars, last pushed 2d ago), licensed MIT. It adds 99 tokens to every session and 806 once invoked, about $0.0004 per session on Opus 5.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-10-26.
Other skills, from other repositories
rtk-optimizer
Wrap high-verbosity shell commands with RTK to reduce token consumption. Use when running git log, git diff, cargo test, pytest, or other verbose CLI output that wastes context window tokens.
session-save
Save the current session state (decisions, modified files, current status, and next steps) to a handoff file for later resume.
handoff-create
Generate a structured handoff document from the current session. Captures scope, relevant files with line numbers, key discoveries, work completed, current status, next steps, and code snippets. Use before ending a session or handing work to another agent.
handoff-update
Update an existing handoff document with current session progress. Applies section-specific merge rules: append-only for Work Done (never deletes history), replace for Status and Next Steps, merge for Files and Discoveries. Falls back to creating a new handoff if no source file is found.
handoff-resume
Load a handoff document and resume work from where a previous session left off. Parses scope, file references, completed work, and next steps, then checks live state and existing authorization before proceeding.
gmail
Manage Gmail email — drafting, sending, organizing, filters, vacation replies, and inbox analysis.