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/using-planflownpx skills add huangyun111/planflow --skill using-planflowgit 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/using-planflow)<a href="https://agentmods.dev/skills/huangyun111/planflow/using-planflow"><img src="https://agentmods.dev/badge/skills/huangyun111/planflow/using-planflow.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 | $0.00071 | $0.00939 |
| Opus 5 | $0.00036 | $0.00469 |
| Sonnet 5 | $0.00014 | $0.00188 |
| Haiku 4.5 | $0.00007 | $0.00094 |
Grade A, and why
using-planflow 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 4d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PlanFlow — Plan-Driven, Short-Session Workflow
Long conversations degrade: details get lost, context rots, and the agent starts re-deriving or contradicting earlier decisions. PlanFlow routes around this by externalizing state to files and keeping each working session short and focused on exactly one task.
When to use this
- The user hands you a substantial, multi-step goal (a feature, refactor, data pipeline, migration).
- A
PLAN.mdorHANDOFF.mdalready exists in the project — read it FIRST. - The user mentions planning, tasks, checklists, or "fresh session".
For a small one-off change, skip the ceremony and just do it.
The memory spine
PLAN.md(project root): the source of truth for WHAT to do — the work broken into small, ordered, checkbox tasks, each with acceptance criteria and the files it touches.CLAUDE.md: durable decisions and conventions, never to be re-derived.HANDOFF.md: an emergency snapshot, only when a single task runs long.
What goes where (keep the files clean)
Mixing transient state into long-term files is what re-rots your context. Be strict about which file holds what:
PLAN.md— tasks and their status. Nothing else.CLAUDE.md— ONLY decisions that stay true many sessions from now (architecture, naming rules, "always do X", verified findings). Do NOT put here: task status, one-run values (a temporary batch size), one-off paths, or experiment results.HANDOFF.md— a transient snapshot of an in-progress task; overwrite freely.- (optional)
WORKLOG.md— an append-only log of results/experiments if your project produces them, so results never leak intoCLAUDE.md.
How to size a task
A good task is something ONE fresh session can finish without approaching the context limit: one coherent unit (a module, function, fix, or thin slice), doesn't need the whole codebase in context, has a concrete "Done when…" condition, and is ordered so earlier tasks unblock later ones. If a task needs more than ~1 hour or touches many files at once, split it further.
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.
- 4d ago First seen · 71 lines · 71 tokens per session scan A a389c6a17304
using-planflow is a skill published in the GitHub repository huangyun111/planflow (2 stars, last pushed 2mo ago), licensed MIT. It adds 71 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-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…
critical-code-reviewer
Rigorously review code or pull requests for correctness, security, accessibility, maintainability, tests, and edge cases. Use when users request a critical code review, want a guided walkthrough of findings, need implementer-facing feedback, or want to prepare, create, or submit a GitHub pull request review.
shiny-bslib
Build modern Shiny dashboards and applications using bslib (Bootstrap 5). Use when creating new Shiny apps, modernizing legacy apps (fluidPage, fluidRow/column, tabsetPanel, wellPanel, shinythemes), or working with bslib page layouts, grid systems, cards, value boxes, navigation, sidebars, filling layouts, theming…
chief-revenue-officer
Owns the revenue engine end to end: sales, monetization, pricing, customer success, retention, and partnerships. Use this for pricing and packaging decisions, sales strategy and coverage, forecast and pipeline health, churn and expansion, partner and channel strategy, or when marketing-sourced demand is not…