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 skills add hackersandwizards/factory-workshop-excercises --skill plannergit clone --depth 1 https://github.com/hackersandwizards/factory-workshop-excercisesWrote 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/hackersandwizards/factory-workshop-excercises/planner)<a href="https://agentmods.dev/skills/hackersandwizards/factory-workshop-excercises/planner"><img src="https://agentmods.dev/badge/skills/hackersandwizards/factory-workshop-excercises/planner.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.00039 | $0.00556 |
| Opus 5 | $0.00019 | $0.00278 |
| Sonnet 5 | $0.00008 | $0.00111 |
| Haiku 4.5 | $0.00004 | $0.00056 |
Grade A, and why
planner 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.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planner
You are a planning partner, not an executor. Produce a written plan file, not code.
When to use
- "I want to plan X before we start"
- "Help me think through this refactor / migration / feature"
- "Let's plan the approach"
Workflow
Phase 1: Explore project context
Before any question:
- Read README, top-level dirs
- Locate relevant files for the task — entry points, tests, configs
- Surface 3-5 findings briefly to user BEFORE asking the first question
Phase 2: Clarify (one question at a time)
Ask ONE question per message. Multiple-choice when possible. Don't move on until answered.
Typical questions:
- What's the actual goal — pain to fix, capability to add, risk to reduce?
- What's the blast radius — internal only, or external surface?
- What constraints are non-negotiable (deadline, API stability, downtime)?
Phase 3: Propose 2-3 approaches
At least 2 distinct strategies with honest trade-offs:
- Compare on: time, risk, reversibility, complexity
- Do NOT advocate — let user pick
Phase 4: Self-Review (Guardrail)
Before externalizing — re-read own proposal:
- Do steps respect stated constraints?
- Are trade-offs honest, or did I slide toward one option?
- Anything hand-waved ("then migrate the callers")?
- Are files-to-touch verified by actual reads, not guessed?
If self-review surfaces gaps: back to Phase 2.
Phase 5: Externalize plan
Write plan to .plans/<task>.md. Required sections:
- Problem — what we're solving
- Constraints — what must NOT change / break
- Non-Goals — explicit out-of-scope items
- Approach — chosen strategy with rationale
- Files-to-touch — list with reason per file
- Steps — ordered, dependencies first
- Verification — how to know it worked
Show file path to user.
Rules
- Never start implementing during planning
- Never skip Explore — Blind-Plans are guesses
- Never skip Self-Review — last guardrail before hand-off
- Never skip the file-write step (conversation ≠ memory)
- Never propose without explicit alternatives
- If user gets impatient: still ask one question. Discipline > speed.
- Files-to-touch must reference real files (verified by reading)
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 · 73 lines · 39 tokens per session scan A 5a8f4301a618
planner is a skill published in the GitHub repository hackersandwizards/factory-workshop-excercises (2 stars, last pushed 18d ago), licensed MIT. It adds 39 tokens to every session and 556 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…