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/fakoli/fakoli-plugins/plannpx skills add fakoli/fakoli-plugins --skill plangit clone --depth 1 https://github.com/fakoli/fakoli-pluginsWrote 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/fakoli/fakoli-plugins/plan)<a href="https://agentmods.dev/skills/fakoli/fakoli-plugins/plan"><img src="https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/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 | $0.00016 | $0.02491 |
| Opus 5 | $0.00008 | $0.01246 |
| Sonnet 5 | $0.00003 | $0.00498 |
| Haiku 4.5 | $0.00002 | $0.00249 |
Grade B, and why
plan scanned grade B with 1 finding 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 3d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
grep '"version"' ~/.claude/plugins/cache/fakoli-plugins/fakoli-crew/*/.claude-plugin/plugin.json 2>/dev/null \ How it starts
The opening of the file, as written. The whole thing — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan — Plan Phase
Read an approved spec, verify assumptions with a scout, write an intent-driven task list, and hand off to /fakoli-flow:execute. Plans describe WHAT to achieve — never HOW to implement it.
Process Flow
Start
|
v
[1. Read the spec]
Load the approved spec file from brainstorm.
Note: goal, components, constraints, acceptance criteria.
|
v
[2. Scout phase]
If fakoli-crew is installed: dispatch scout to verify assumptions.
Wait for scout status file. Read findings before writing any task.
|
v
[3. Map files and responsibilities]
Identify which files will be created or modified.
Assign clear ownership — one task per file group.
|
v
[4. Write intent-driven tasks]
For each task: intent, acceptance criteria, scope, agent, verify, depends on.
No code. No step-by-step instructions. Acceptance criteria only.
|
v
[5. Self-review]
Check: spec coverage, criteria clarity, dependency graph, agent assignments.
Fix issues inline.
|
v
[6. Save plan]
Save to docs/plans/<YYYY-MM-DD>-<feature>.md
(or the path CLAUDE.md specifies).
|
v
[7. Hand off to /fakoli-flow:execute]
Step-by-Step Rules
Step 1: Read the Spec
Load the spec file (passed by brainstorm or provided by the user). Extract:
- The goal (one sentence)
- All stated requirements and acceptance criteria
- Architectural decisions and constraints
- Out-of-scope items (these must NOT appear as tasks)
If no spec file is provided, ask for it before proceeding. Do not plan from memory of a conversation — the spec is the source of truth.
Step 2: Scout Phase
If fakoli-crew is installed: dispatch a scout agent before writing any task.
First, derive a scratch path for this planning session. Use a plan- prefixed run ID:
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.
- 3d ago First seen · 270 lines · 16 tokens per session scan B 0cb89092cfa5
plan is a skill published in the GitHub repository fakoli/fakoli-plugins (4 stars, last pushed 25d ago), licensed MIT. It adds 16 tokens to every session and 2,491 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
deno-knowledge-patch
Use this skill when choosing current Deno runtime APIs, CLI options, configuration, dependency behavior, Node compatibility, or deployment workflows. Open the topic reference before changing a project because several commands, flags, APIs, and defaults changed more than once.
apache-kafka-knowledge-patch
Use this skill when upgrading, configuring, extending, or operating Apache Kafka and its clients, Kafka Streams, Kafka Connect, MirrorMaker, KRaft, share groups, or tiered storage. Inspect the project's actual broker, client, metadata, and Java versions before applying version-dependent advice.
authjs-knowledge-patch
Use this patch to choose the maintained authentication path, avoid security-sensitive provider mistakes, and apply current Auth.js integration patterns. Read the topic reference before changing an affected flow; the quick reference prioritizes breaking behavior, security updates, and common implementation work.
clerk-knowledge-patch
Use this guide when implementing, upgrading, or debugging Clerk authentication, authorization, Organizations, Billing, SDKs, components, or deployment architecture. Start with the migration notes, then open the matching reference.
clickhouse-knowledge-patch
Use this skill when writing, reviewing, upgrading, or operating ClickHouse SQL and server configurations. Start with the compatibility-sensitive items below, then load the topic reference that matches the task.
airflow-knowledge-patch
Use this skill when authoring, upgrading, integrating, or operating Apache Airflow. Start with the quick guidance below, then open the topic reference that matches the work.