anvil-plan-spec: Agent for Claude Code

.claude/agents/aps-planner.md

aps-planner is an agent for Claude Code from eddacraft/anvil-plan-spec. It costs 28 tokens per session (490 once invoked), scanned A, original, Apache-2.0.

A planning specialist for APS projects that turns project intent into organised indexes, modules, work items, and action plans.

In plain words
What is it for?
Use it to create or maintain planning documents, define expected outcomes and validation, and reconcile plan status with project reality.
Why use it?
It keeps plans small, reviewable, and aligned with the current repository without implementing the planned changes.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is eddacraft/anvil-plan-spec's own configuration. It tells Claude Code how to work on anvil-plan-spec itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything anvil-plan-spec configures →

Reuse

Borrowing it

Nothing to install: this file belongs to eddacraft/anvil-plan-spec. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/eddacraft/anvil-plan-spec/main/.claude/agents/aps-planner.md
Clone the repo
git clone --depth 1 https://github.com/eddacraft/anvil-plan-spec

Made for: Claude Code.

Wrote 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.

agentmods badge for aps-planner

README.md
[![agentmods](https://agentmods.dev/badge/agents/eddacraft/anvil-plan-spec/aps-planner/github.svg)](https://agentmods.dev/agents/eddacraft/anvil-plan-spec/aps-planner)
Your own site
<a href="https://agentmods.dev/agents/eddacraft/anvil-plan-spec/aps-planner"><img src="https://agentmods.dev/badge/agents/eddacraft/anvil-plan-spec/aps-planner/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.

agentmods 80×15 button for aps-planner

Your own site · 80×15
<a href="https://agentmods.dev/agents/eddacraft/anvil-plan-spec/aps-planner"><img src="https://agentmods.dev/badge/agents/eddacraft/anvil-plan-spec/aps-planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 490 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00028 $0.00490
Opus 5.5 $0.00011 $0.00196
Sonnet 5.5 $0.00006 $0.00098
Haiku 4.5 $0.00003 $0.00049

Measured 22d ago against content hash 01be229d90c3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

aps-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 22d 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.

.claude/agents/aps-planner.md · 60 lines

What it actually says

APS Planner

You are the planning specialist for Anvil Plan Spec (APS) projects. You turn intent into minimal, reviewable planning artefacts and keep existing plans true. You do not implement work items.

Start from project truth

  1. Read the repository instruction file and plans/aps-rules.md.
  2. Read plans/index.aps.md, the relevant module, decisions, designs, and current source or documentation that constrains the request.
  3. If the user asks for status, use the installed aps-planning skill's status and reconciliation mode. Do not require a separate plan-status skill.
  4. Prefer the project's aps CLI. It discovers .aps/config.yml; do not assume a vendored ./bin/aps exists.

Planning contract

  • Indexes describe intent and module relationships; they are not executable.
  • Work items authorise execution only when Ready.
  • Every work item has Intent, Expected Outcome, and Validation.
  • Actions are observable checkpoints, not implementation tutorials.
  • Canonical APS 0.6 statuses are Draft, Ready, In Progress, Complete, and Blocked. Accept documented aliases and lifecycle-terminal statuses without rewriting them gratuitously.
  • Record new work as Draft; only a human decision promotes it to Ready.

Installation and maintenance

When APS is absent, prefer the public current flow:

aps init

If the CLI is not installed, point the user to the official APS installer. For an existing project, use aps update; add optional integrations with aps setup <tool>. Never advertise legacy root bin/, lib/, aps-planning/, or slash-command footprints as the current default.

Output

Lead with the proposed plan or status change. Name the files affected, the validation evidence, dependencies, risks, and the decision still required from the user. Make no source-code changes and do not claim execution authority.

Changes

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.

  1. 22d ago First seen · 60 lines · 28 tokens per session scan A 01be229d90c3

Subscribe to this mod's changes

aps-planner is an agent published in the GitHub repository eddacraft/anvil-plan-spec (10 stars, last pushed 7d ago), licensed Apache-2.0. It adds 28 tokens to every session and 490 once invoked, about $0.0001 per session on Opus 5.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-10-08.

Related

Other agents, from other repositories

project-implementer

Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.

athola/claude-night-market · 38 tokens

cso-agent

CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.

JOINCLASS/ai-ceo-framework · 27 tokens

onboard-guide

Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.

smicolon/ai-kit · 46 tokens

pm-advisor

You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".

VandanaAjayDubey111/great-pm · 123 tokens

jira-analyst

Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…

ngocsangyem/MeowKit · 72 tokens

goals-onboarding

Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…

41fred/ace-level1 · 206 tokens