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 eddacraft/anvil-plan-spec --skill aps-planninggit clone --depth 1 https://github.com/eddacraft/anvil-plan-specWrote 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/eddacraft/anvil-plan-spec/aps-planning)<a href="https://agentmods.dev/skills/eddacraft/anvil-plan-spec/aps-planning"><img src="https://agentmods.dev/badge/skills/eddacraft/anvil-plan-spec/aps-planning.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.00036 | $0.02358 |
| Opus 5 | $0.00018 | $0.01179 |
| Sonnet 5 | $0.00007 | $0.00472 |
| Haiku 4.5 | $0.00004 | $0.00236 |
Grade A, and why
aps-planning 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 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.
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 — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
APS Planning Skill
Activation Guard
If plans/index.aps.md does not exist in the current project, do nothing.
This skill is inert in projects without APS plans. Do not mention APS, do not
offer to create plans, do not load any context. Silently skip all sections
below.
Session Start -- Load Context
When a session begins and plans/index.aps.md exists, build APS awareness in
working memory. Do this quietly -- do not print output to the user unless they
ask about plan status.
Step 1: Read the index
Read plans/index.aps.md. Extract the Modules table. Identify active modules
-- those whose status is NOT Done, Complete, Merged, Released, Shipped,
Released/Shipped, or Archived. Note the plan title and any current-window
notes.
Step 2: Read active modules
For each active module, read its .aps.md file from plans/modules/. Extract
all work items with their fields:
- ID (e.g.,
AUTH-001) - Title
- Status (the native APS CLI currently transitions
Draft,Ready,In Progress,Complete, andBlocked; it recognisesProposedasDraftandDoneasComplete. This catalogue additionally follows ADR-0013:Merged/Released/Shipped/Released/Shippedare post-merge lifecycle states — not selectable for implementation;Mergedis interim and advances toCompleteonly on release or ship evidence) - Files (from the
Files:field, if present) - Validation (from the
Validation:field) - Priority (if specified)
- Dependencies (if specified)
Skip work items with inactive/completed statuses: Done, Complete, Merged,
Released, Shipped, Released/Shipped, or Archived.
Step 3: Build the file-to-item map
From all non-Complete work items that have a Files: field, build a mapping of
file paths to work item IDs. This map is used during passive awareness to
recognise when edited files relate to planned work.
Example:
src/auth/login.ts -> AUTH-001, AUTH-003
src/db/migrations/ -> DB-002
packages/core/src/policy.ts -> POL-001
What ships with it
16 files 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.
- examples.md 4.6 KB
- hooks.md 6.1 KB
- README.md 4.4 KB
- reference.md 4.2 KB
- scripts/check-complete.ps1 3.7 KB runs code
- scripts/check-complete.sh 2.9 KB runs code
- scripts/enforce-plan-update.ps1 4.1 KB runs code
- scripts/enforce-plan-update.sh 3.4 KB runs code
- scripts/init-session.ps1 4.5 KB runs code
- scripts/init-session.sh 3.5 KB runs code
- scripts/install-hooks.ps1 8.8 KB runs code
- scripts/install-hooks.sh 6.4 KB runs code
- scripts/post-tool-nudge.ps1 430 B runs code
- scripts/post-tool-nudge.sh 448 B runs code
- scripts/pre-tool-check.ps1 557 B runs code
- scripts/pre-tool-check.sh 515 B runs code
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 Changed · -20 lines · -4 tokens per session scan C → A 838cbadccfeb
- 8d ago First seen · 294 lines · 40 tokens per session scan C b6cebca9c558
aps-planning is a skill published in the GitHub repository eddacraft/anvil-plan-spec (10 stars, last pushed today), licensed Apache-2.0. It adds 36 tokens to every session and 2,358 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-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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…