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 skills/tony/skills/02-plannpx skills add tony/skills --skill 02-plangit clone --depth 1 https://github.com/tony/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/tony/skills/02-plan)<a href="https://agentmods.dev/skills/tony/skills/02-plan"><img src="https://agentmods.dev/badge/skills/tony/skills/02-plan.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.00027 | $0.00683 |
| Opus 5 | $0.00014 | $0.00342 |
| Sonnet 5 | $0.00005 | $0.00137 |
| Haiku 4.5 | $0.00003 | $0.00068 |
Grade A, and why
02-plan 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 2d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
02-plan
Turn measured candidates into a reviewable commit plan. This phase only reads
the suite and writes plan.json; it makes no code changes.
$ARGUMENTS may pass --max-commits=N to cap the plan, --min-score to raise the
inclusion threshold, and --force to recompute.
Step 1: Load and score
Read benchmarks.json and baseline.json. Score every validated candidate with
../../references/scoring-rubric.md:
total = 0.35*safety + 0.30*impact + 0.15*effort
+ 0.12*confidence + 0.08*reversibility
Apply the hard gates first: drop any candidate with safety < 0.4 or
impact == 0. For each dropped item, capture the prerequisite refactor (if any)
as a separate, clearly-labeled follow-up — not as an auto-applied commit.
Step 2: Order
Score sets priority; these constraints override it where they apply:
- Safety-gate fixes first (make collection deterministic, prove order independence) before any parallel/reorder speedup.
- Typing and parametrize migrations early (low-risk, readable diffs).
- Scope and consolidation before parallelism.
- One speedup per commit — never bundle.
Honor --max-commits / --min-score.
Step 3: Draft commits
For each planned item, draft a commit from
../../templates/commit-message.tmpl, adapting the
type(scope) prefix to the target project's convention (read from its
AGENTS.md/CLAUDE.md). Each entry records: order, heuristic id, the score
breakdown, target files, the draft subject/body, the verify command (the project
test + quality checks), and any depends_on. Write plan.json and update
state.json (phase=plan, plan hash).
Step 4: Present for approval (plan mode)
This phase is a decision point. Enter plan mode (Claude Code: EnterPlanMode;
others: /plan or Shift+Tab). Present the 02-plan sections from
../../references/output-contract.md: ## Ranked plan,
## Dropped at the gate, ## Ordering rationale. Let the user reorder, drop
items, or cap the count. Because plan mode is the decision point, omit the
AskUserQuestion panel here. Exit plan mode once approved; plan.json is the
contract /pytest-optimizer:03-execute consumes.
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.
- 2d ago First seen · 64 lines · 27 tokens per session scan A e2cd5df8b870
02-plan is a skill published in the GitHub repository tony/skills (2 stars, last pushed 7d ago), licensed MIT. It adds 27 tokens to every session and 683 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-09-03.
Other skills, from other repositories
postgres-database-migration
Use this skill for planning, testing, and safely executing PostgreSQL schema migrations — especially when working with production data or shared databases. Trigger when user asks to: Test a schema migration before applying it to production Add, remove, or rename columns safely on a live table Change a column's data…
design-postgis-tables
Comprehensive PostGIS spatial table design reference covering geometry types, coordinate systems, spatial indexing, and performance patterns for location-based applications.
setup-timescaledb-hypertables
Use this skill when creating database schemas or tables for Timescale, TimescaleDB, TigerData, or Tiger Cloud, especially for time-series, IoT, metrics, events, or log data. Use this to improve the performance of any insert-heavy table. Trigger when user asks to: Create or design SQL schemas/tables AND…
pgvector-semantic-search
Use this skill for setting up vector similarity search with pgvector for AI/ML embeddings, RAG applications, or semantic search. Trigger when user asks to: Store or search vector embeddings in PostgreSQL Set up semantic search, similarity search, or nearest neighbor search Create HNSW or IVFFlat indexes for vectors…
postgres-hybrid-text-search
Use this skill to implement hybrid search combining BM25 keyword search with semantic vector search using Reciprocal Rank Fusion (RRF). Trigger when user asks to: Combine keyword and semantic search Implement hybrid search or multi-modal retrieval Use BM25/pgtextsearch with pgvector together Implement RRF (Reciprocal…
find-hypertable-candidates
Use this skill to analyze an existing PostgreSQL database and identify which tables should be converted to Timescale/TimescaleDB hypertables. Trigger when user asks to: Analyze database tables for hypertable conversion potential Identify time-series or event tables in an existing schema Evaluate if a table would…