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/huangyun111/planflow/plannpx skills add huangyun111/planflow --skill plangit clone --depth 1 https://github.com/huangyun111/planflowWrote 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/huangyun111/planflow/plan)<a href="https://agentmods.dev/skills/huangyun111/planflow/plan"><img src="https://agentmods.dev/badge/skills/huangyun111/planflow/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.00040 | $0.00433 |
| Opus 5 | $0.00020 | $0.00217 |
| Sonnet 5 | $0.00008 | $0.00087 |
| Haiku 4.5 | $0.00004 | $0.00043 |
Grade A, and why
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 5d 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
You are setting up PLAN.md for a task. Do NOT write implementation code yet.
The user's goal: $ARGUMENTS
- Restate the goal in 1-2 sentences. If something critical is ambiguous, ask up to 3 sharp questions first — otherwise proceed.
- Briefly explore the relevant code so the plan is grounded in reality.
- Decompose the goal into small, ordered, independently-completable tasks. A good task is something ONE fresh session can finish without approaching the context limit (a module, function, fix, or thin slice), needs only a few files in context, and has a concrete "Done when…" condition. If a task needs more than ~1 hour or touches many files at once, split it further.
- Write ./PLAN.md as:
Plan —
Goal
<1-2 sentences>Notes / Constraints
- Self-check the plan before showing it. Every task must have Files, Do, and a Done-when; each "Done when…" must be concretely checkable — a command to run, a file that appears, an observable output — never vague like "improve X" or "make it better". Tasks must be small (one fresh session each) and ordered by dependency. Rewrite any task that fails this bar.
- Show the plan and ask the user to confirm or adjust before any coding.
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.
- 5d ago First seen · 38 lines · 40 tokens per session scan A 8da0a2bc7932
plan is a skill published in the GitHub repository huangyun111/planflow (2 stars, last pushed 2mo ago), licensed MIT. It adds 40 tokens to every session and 433 once invoked, about $0.0002 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 skills, from other repositories
meta-tags-optimizer
Optimize title tags, meta descriptions, Open Graph, and Twitter cards for maximum click-through rate. Generates multiple A/B test variations with character counting and SERP preview. Use when asked to "optimize title tag", "write meta description", "improve CTR", "Open Graph tags", "fix my meta tags", "social media…
google-ads-audit
Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…
sxo
Search Experience Optimization (SXO) — the bridge between SEO and UX/CRO. Audits the full journey from the SERP click to the on-page goal: SERP click-through factors (title/meta/rich results that win the click), then post-click experience signals that keep users and drive conversions — above-the-fold relevance and…
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
security
Enforce Elixir/Phoenix security — auth, OAuth, sessions, CSRF, XSS, SQL injection, input validation, secrets. Use when editing auth files, login flows, RBAC, or API keys.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.