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 mthines/agent-skills --skill aw-create-plangit clone --depth 1 https://github.com/mthines/agent-skillsWrote 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/mthines/agent-skills/aw-create-plan)<a href="https://agentmods.dev/skills/mthines/agent-skills/aw-create-plan"><img src="https://agentmods.dev/badge/skills/mthines/agent-skills/aw-create-plan.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 214 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- medium Prompt Injection · line 104 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
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.00150 | $0.06254 |
| Opus 5 | $0.00075 | $0.03127 |
| Sonnet 5 | $0.00030 | $0.01251 |
| Haiku 4.5 | $0.00015 | $0.00625 |
Grade A, and why
aw-create-plan scanned grade A 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
run: "curl -s -o /dev/null -w '%{http_code}' localhost:3000/me -H 'Authorization: Bearer $EXPIRED'" How it starts
The opening of the file, as written. The whole thing — 495 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Plan Artifact
Generate .agent/{branch-name}/plan.md — the planner→executor handoff document — alongside checks.yaml, the executable acceptance checks derived from the Acceptance Criteria.
A new Claude session MUST be able to execute from plan.md alone without the original conversation.
plan.md is a handoff artifact, not an exhaustive knowledge base. Keep it lean (see the Core/Extended tiering in Step 2). checks.yaml is the living contract — it is re-derived on every iteration (statuses reset to pending) and self-validates against reality on every executor loop, so it does not go stale the way prose does. When something is unclear, prefer asking the still-running planner agent (or the user) over bloating the document to answer every future question.
Snapshot mode (opt-in)
By default this skill writes only plan.md (overwritten in place each iteration; the version: frontmatter is the iteration counter). .agent/ is gitignored per-developer scratch, so immutable plan.vN.md snapshot chains are not written by default — they are rarely re-read and cost a redundant write per iteration, with no measured effect on task success (research §5.4).
Opt in to snapshots with Skill("aw-create-plan", "snapshot") — then the skill also writes an immutable plan.v{N}.md alongside plan.md (plan.v1.md, plan.v2.md, … as history) for a durable audit trail of the plan's evolution. Everything below marked (snapshot mode) applies only then.
How the mode arg is read (disambiguation)
The arg slot is overloaded — some callers pass a short mode flag, others a whole plan body. Resolve it before anything else: snapshot mode is on iff the trimmed arg is exactly snapshot or --snapshot (case-insensitive, a single bare token). Every other arg — empty, or a multi-line plan.md body — is default mode (no snapshot). In particular, orchestrators like /fix-bug pass the whole plan body here (Skill("aw-create-plan", "<full plan.md body>")), which is default mode by design — the fast lane opts out of snapshots anyway.
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 · 495 lines · 150 tokens per session scan A 99d1db67249e
aw-create-plan is a skill published in the GitHub repository mthines/agent-skills (13 stars, last pushed today), licensed MIT. It adds 150 tokens to every session and 6,254 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
ego-browser
Skill "ego-browser" from citrolabs/ego-lite, covering ego-browser, quick start, common helpers, task spaces and control handoff.
temporal-developer
Develop, debug, and manage Temporal applications across Python, TypeScript, Go, Java, .NET, Ruby, and Rust. Use when the user is building workflows, activities, or workers with a Temporal SDK, debugging issues like non-determinism errors, stuck workflows, or activity retries, using Temporal CLI, Temporal Server, or…
geekx-gate
A review framework for deciding whether an engineering idea or technical commitment is necessary, too broad, or premature. It examines the real problem, complexity, evidence, non-goals, and ease of reversal.
geekx-engineering
A set of engineering instructions for making substantial changes in an existing codebase. It emphasizes understanding the affected system, keeping a persistent plan, and recording decisions and evidence.
x-algorithm
Write X (Twitter) posts that the For You algorithm actually rewards. Grounded in the open-sourced X recommendation system — the Grok-based transformer ranker, Phoenix retrieval, Thunder in-network store, and Grox content-understanding pipeline. Use when the user wants to write a post, thread, reply, or quote; plan a…
opencode-memory
Browse local OpenCode history: sessions, messages, plans, prompt history, and prior decisions. Use when the user says history, previous session, last time, remember, recall, plans, prior work, or when resuming/debugging repeated work where earlier OpenCode context may help. Do not use for fresh tasks or when current…