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/nextnpx skills add huangyun111/planflow --skill nextgit 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/next)<a href="https://agentmods.dev/skills/huangyun111/planflow/next"><img src="https://agentmods.dev/badge/skills/huangyun111/planflow/next.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.00048 | $0.00460 |
| Opus 5 | $0.00024 | $0.00230 |
| Sonnet 5 | $0.00010 | $0.00092 |
| Haiku 4.5 | $0.00005 | $0.00046 |
Grade A, and why
next 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
Execute the next unfinished task from ./PLAN.md. One task, then stop.
- Read PLAN.md, find the first unchecked [ ] task.
- Read ONLY the files listed under that task's "Files" (plus what they directly need). Do not load the whole repo.
- Implement just that task — nothing borrowed from later tasks.
- Verify against "Done when…" with real evidence. Actually run the relevant
test / command / check and look at the output — do not assume it passed.
- If it does NOT pass: leave the box UNCHECKED, append a one-line blocker note under the task, and stop. Never tick a box you could not verify.
- Only if verification passed, update PLAN.md: tick the box and append a
one-line result note, e.g.
- [x] T1 — … ✔ <what was done>. - If a durable decision/convention emerged, add it to the project's CLAUDE.md. Durable = a rule still true many sessions from now. Do NOT put transient state, one-off values, paths, or results in CLAUDE.md (those go in the task note, HANDOFF.md, or an append-only WORKLOG.md).
- Print a closure summary before stopping:
- Changed files — if this is a git repo, run
git diff --stat; otherwise list them. - The exact command(s) you ran to verify, and their result.
- A one-line suggested commit message. (Do NOT commit unless asked.)
- Changed files — if this is a git repo, run
- STOP. Summarize in 2-3 lines and tell the user to open a fresh session and run this skill again for the next task. Do NOT continue to the next task in this conversation.
If context grows long before finishing, write HANDOFF.md and stop.
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 · 33 lines · 48 tokens per session scan A 784d45653c34
next is a skill published in the GitHub repository huangyun111/planflow (2 stars, last pushed 2mo ago), licensed MIT. It adds 48 tokens to every session and 460 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.
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.
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.