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 Mathews-Tom/armory --skill plan-promptsgit clone --depth 1 https://github.com/Mathews-Tom/armoryWrote 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/mathews-tom/armory/plan-prompts)<a href="https://agentmods.dev/skills/mathews-tom/armory/plan-prompts"><img src="https://agentmods.dev/badge/skills/mathews-tom/armory/plan-prompts.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00087 | $0.03492 |
| Opus 5 | $0.00044 | $0.01746 |
| Sonnet 5 | $0.00017 | $0.00698 |
| Haiku 4.5 | $0.00009 | $0.00349 |
Grade A, and why
plan-prompts 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Development Plan and Execution Prompts
Convert source documents into a plan that remains valid as milestones merge:
.docs/DEVELOPMENT_PLAN.md— the committed, authoritative milestone plan..docs/EXECUTION_PROMPTS.md— the committed, authoritative/goalcontract for each milestone..docs/DEVELOPMENT_PLAN_HISTORY.md— the single local, append-only design-evidence ledger. It must be gitignored.
This skill plans from documents only. Do not implement product code, create branches, open PRs, or execute the generated prompts.
Scope Boundary
| Situation | Package |
|---|---|
| Destination or the decisions needed to define it remain uncertain | decision-map |
Inputs
Accept either input shape:
| Input shape | Meaning |
|---|---|
| Folder path | Recursively ingest every supported document in that folder. |
| Explicit file list | Ingest listed files only; treat the first file as the primary source of truth. |
Optional context:
| Field | Meaning | Default |
|---|---|---|
REPO_CONTEXT |
Target repo path or description; inspect its current structure, tooling, CI, style, release conventions, and partial implementation. | Greenfield planning if absent. |
GLOBAL_CONSTRAINTS |
Cross-cutting constraints absent from source docs. | None. |
STACK_DEPTH_HINT |
Maximum PRs per milestone stack. | 6. |
Workflow
Phase 0 — Ingest and ground the plan
- Inventory every capability, contract, data model, integration, workflow, and non-functional requirement in the source docs.
- Preserve source order, but resolve authority by input shape: explicit file-list order wins; otherwise newer or more-specific design docs refine broader overview docs.
- Build a traceability table from source references to planned capabilities. Use document paths plus section names or line ranges when available.
- Record
> ASSUMPTION:for defensible defaults. Record> GAP:for missing, ambiguous, or contradictory requirements. A contradiction affecting architecture, data semantics, security posture, or acceptance blocks output until resolved. - Map implementation-relevant dependencies. Inspect the target repo when available: CI, package manager, test/type/lint commands, naming conventions, partial implementations, version source,
CHANGELOG.md, tags, branches, and release commands. - Identify source-traceable release targets and group milestones into shared release trains. Every milestone must target a named release,
unversioned,none, or visible> GAP:. Never infer a version. - For a greenfield repo, make M1 establish the minimum verification surface required by later milestones.
- If existing plan/prompt artifacts are present, read them before regenerating. Treat them as the current committed contract, not as immutable truth.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 232 lines · 87 tokens per session scan A deea84e60766
plan-prompts is a skill published in the GitHub repository Mathews-Tom/armory (316 stars, last pushed 2d ago), licensed MIT. It adds 87 tokens to every session and 3,492 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-30.
Other skills, from other repositories
openagentskill-registry
Discover, compare, audit, and safely install reusable AI Agent Skills with OpenAgentSkill. Use whenever an agent needs a capability it does not already have, must compare Skill alternatives, or needs evidence before installing third-party instructions.
manager
A session-to-GitHub tracker that creates, updates, and reads issues across repositories, including their labels, parent epics, and project-board placement.
weekly-retro
A structured weekly retrospective for a one-person business run with AI agents. It gathers evidence from code, project tools, and canonical business files, then records findings and outcomes.
art-director
Orchestrate iterative visual style searches with branch prompts, decision graphs, feedback loops, and final direction selection.
html-draft
Use when user wants a standalone HTML diagram in flat engineering blueprint style — architecture diagrams, system flows, technical spec sheets, component maps. Generates one HTML file using Tailwind v4 (browser CDN) for layout and D3 v7 (CDN) for SVG diagrams. User-invoked only — do NOT auto-trigger. Triggers on…
pm-metrics
A product-metrics review aid that examines trends, unusual changes, possible causes, and recommended actions. It can organize a main product metric into lower-level measures, inspect retention and funnels, read A/B tests, and compare results with goals.