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 FarzamMohammadi/the-engineer --skill create-plangit clone --depth 1 https://github.com/FarzamMohammadi/the-engineerWrote 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/farzammohammadi/the-engineer/create-plan)<a href="https://agentmods.dev/skills/farzammohammadi/the-engineer/create-plan"><img src="https://agentmods.dev/badge/skills/farzammohammadi/the-engineer/create-plan/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/farzammohammadi/the-engineer/create-plan"><img src="https://agentmods.dev/badge/skills/farzammohammadi/the-engineer/create-plan.svg" alt="Reviewed on agentmods" width="80" 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.00123 | $0.01438 |
| Opus 5 | $0.00062 | $0.00719 |
| Sonnet 5 | $0.00025 | $0.00288 |
| Haiku 4.5 | $0.00012 | $0.00144 |
Grade A, and why
create-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 9d 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Plan
You own the plan. Requirements gathered intent. Research mapped the codebase. Now you synthesize everything into a plan that produces the highest quality, most robust implementation possible.
Take full ownership. Previous phases did their best, but they may have missed things. You are the last line of defense before code gets written. Be diligent. Be meticulous. Cover gaps that earlier phases might have overlooked. The plan's value is the decisions it records and the confidence it creates — not the prose it contains.
Phase 1: Absorb
Read ALL upstream artifacts fully before designing anything:
- Requirements document (check
.claude/temp/requirements-gathering/) - Research document (check
.claude/temp/research/) - Any other referenced files, tickets, or context
Absorb everything. Cross-reference requirements against research findings. Look for:
- Requirements that research findings complicate or contradict
- Research findings that requirements didn't account for (especially cross-cutting concerns)
- Gaps that neither phase caught — things you can see now with both documents side by side
- Edge cases, error paths, and failure modes that need explicit handling in the plan
Surface anything you find. This is your diligence step.
Phase 2: Design
Synthesize all accumulated context into a complete plan draft. Design for robustness, quality, and correctness — not just the happy path. Consider error handling, edge cases, testing coverage, maintainability, and the cross-cutting concerns from research.
Present the full draft to the user. Walk through the key decisions with your reasoning:
Decision: [Title] My recommendation: [Choice] because [reasoning from research] Alternative: [Option B] — [trade-off] What this locks in: [Consequence of choosing]
Iterate with the user until aligned on all decisions. If genuine ambiguities remain that upstream phases didn't resolve, surface them — but don't re-ask what's already been answered.
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.
- 9d ago First seen · 171 lines · 123 tokens per session scan A 9eed95477a14
create-plan is a skill published in the GitHub repository FarzamMohammadi/the-engineer (12 stars, last pushed 1mo ago), licensed MIT. It adds 123 tokens to every session and 1,438 once invoked, about $0.0006 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-30.
Other skills, from other repositories
doubt-driven-review
In-flight adversarial check on a non-trivial decision BEFORE it stands — distinct from post-hoc review of a finished diff. Use on "stress-test this decision", "are we sure about this", "verify before commit", "poke holes in this", when working in unfamiliar code, or before an irreversible step (migration, prod deploy…
release-cut
Cut a new pi-agent-dashboard release: promote ## [Unreleased] in CHANGELOG.md, bump every workspace package.json per SemVer, commit, tag v , and push — triggering the Release workflow that publishes every non-private workspace, builds the Electron artifacts, and creates a GitHub Release. Use on "cut a release"…
spec-coherence-check
Sweep all active OpenSpec proposals for staleness, conflicts, and obsolescence against the current codebase and archived changes. Use when proposals may be outdated, when checking cross-proposal conflicts, or before starting a batch of implementations. Produces a gap-analysis report, updates a priority queue file, and…
ship-it
Worktree-side implementation orchestrator for an OpenSpec change. Idempotent: gates automated scenarios on filesystem reality, owns the red-test fix loop, runs the docker harness with always-teardown, then drives ship-change inline. Escape hatch writes SHIPITBLOCKED.md. Runnable headless. Triggers: "ship it", "build…
faq-mine
Mine docs/faq.md from README.md, docs/.md, and the pi-hermes memory stores. Dispatches @fast subagents per source, dedupes against the existing FAQ, and merges entries in caveman style. Use when asked to "build / regenerate / extend the FAQ", "mine docs into FAQ", "mine hermes memory into FAQ", "surface runtime…
session-to-guideline
Turn a pi session into a Markdown "how-we-did-it" collaboration guideline: reads the session's JSONL transcript and synthesizes a reusable playbook of which prompts worked, what had to be steered, and how to reproduce the result faster. Use when: "document this session", "write up how we did X with the AI", "make a…