Borrowing it
Nothing to install: this file belongs to jaysonmulwa/flanner. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jaysonmulwa/flanner/main/.claude/skills/flanner-plan/SKILL.mdgit clone --depth 1 https://github.com/jaysonmulwa/flannerWrote 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/jaysonmulwa/flanner/flanner-plan)<a href="https://agentmods.dev/skills/jaysonmulwa/flanner/flanner-plan"><img src="https://agentmods.dev/badge/skills/jaysonmulwa/flanner/flanner-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.00071 | $0.00267 |
| Opus 5 | $0.00036 | $0.00133 |
| Sonnet 5 | $0.00014 | $0.00053 |
| Haiku 4.5 | $0.00007 | $0.00027 |
Grade A, and why
flanner-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 8d 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
Saving a plan through flanner
This repo manages planning docs with flanner. Do not write them with the Write tool; the plan directory and header are handled by the MCP tools.
- Confirm intent. If it is ambiguous whether a markdown file is a plan (versus a README, changelog, or notes), ask the user before proceeding.
- Resolve the target with
get_plan_configandlist_projects. - Create with
create_plan_file_tool(project_id, name, content), passing the markdown body WITHOUT frontmatter; the header is added for you. - Revise an existing plan with
update_plan_file_tool(plan_file_id, content), which bumps the version and re-hashes the content.
Never hand-write the YAML header, and never place plan files outside the
directory reported by get_plan_config.
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.
- 8d ago First seen · 26 lines · 71 tokens per session scan A de9c3d4cd553
flanner-plan is a skill published in the GitHub repository jaysonmulwa/flanner (5 stars, last pushed 3d ago), licensed MIT. It adds 71 tokens to every session and 267 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
processing-markdown
Processes Markdown files using mq, a jq-like query language for Markdown. Use when the user mentions Markdown processing, content extraction, document transformation, or mq queries.
web-scraping
Fetches web pages and extracts structured data using mq's toolchain (mq-crawl for fetching/crawling/JS rendering, mq for HTML-to-Markdown selector-based extraction, http() for in-query requests). Use when the user wants to scrape a URL, pull structured data out of a webpage, crawl a site, or turn HTML into…
crit-cli
Use when an agent needs to author or reply to crit inline comments programmatically (including multi-agent workflows commenting on shared code/plans/docs/proposals), publish or unpublish a crit review with crit share, sync a crit review to or from a GitHub PR or GitLab MR, or read/interpret a crit review JSON file.…
crit
Review code changes, a plan, a live page (running dev server), or a local HTML file with Crit inline comments and structured human feedback. Use only when the user explicitly invokes /crit or directly asks to use Crit; a generic review request does not count.
crit-story
Author a crit story and continue the interactive review loop only when the user explicitly invokes crit-story or directly asks you to generate a crit story. Do not infer this skill from generic review, PR, or diff-review requests.
slopless
Use Slopless to review English Markdown for deterministic AI and human slop signals, including vague phrasing, formulaic prose, weak rhythm, filler, and cliches.