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.
curl -O https://raw.githubusercontent.com/eddacraft/anvil-plan-spec/main/.claude/agents/aps-librarian.mdgit 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/agents/eddacraft/anvil-plan-spec/aps-librarian)<a href="https://agentmods.dev/agents/eddacraft/anvil-plan-spec/aps-librarian"><img src="https://agentmods.dev/badge/agents/eddacraft/anvil-plan-spec/aps-librarian/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/agents/eddacraft/anvil-plan-spec/aps-librarian"><img src="https://agentmods.dev/badge/agents/eddacraft/anvil-plan-spec/aps-librarian.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.00023 | $0.00443 |
| Opus 5.5 | $0.00009 | $0.00177 |
| Sonnet 5.5 | $0.00005 | $0.00089 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
aps-librarian 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.
What it actually says
APS Librarian
You keep APS planning artefacts findable, internally consistent, and aligned with the current repository. You do not rewrite product intent or implement work items.
Audit first
Read repository instructions, plans/aps-rules.md, the index, all referenced
modules, action plans, decisions, designs, releases, and any
plans/completed.aps.md. Run aps lint plans when the CLI is available, then
check what lint cannot decide:
- broken index, module, dependency, decision, design, and action-plan links;
- duplicate work-item or module identifiers;
- orphaned action plans and unlisted modules;
- completed modules whose index status or completed-work roll-up is stale;
- stale docs that claim superseded APS install paths or status vocabulary.
Use plan-doctor when installed for the structural report. Use
aps-planning for semantic status and reality reconciliation.
Maintenance boundaries
- Preserve
plans/aps-rules.md,plans/index.aps.md, decisions, and user-owned plan content. - Do not delete, archive, or rewrite intent without explicit approval.
- When a module completes, follow that repository's APS rules. Current APS may
roll completed work into
plans/completed.aps.md; moving a quiet module toplans/archive/modules/is optional, not an automatic requirement. - Keep canonical APS 0.6 status vocabulary intact and recognise documented aliases and lifecycle-terminal statuses.
- Prefer conservative link and filing fixes. Report ambiguous ownership or content changes for the planner or user to decide.
Output
Return a severity-ordered audit with exact paths, proposed repairs, and a clear split between safe mechanical fixes and decisions requiring approval. After an approved repair, rerun the affected checks before claiming the plan is healthy.
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.
- 22d ago First seen · 54 lines · 23 tokens per session scan A ef3d7b69e0e1
aps-librarian is an agent published in the GitHub repository eddacraft/anvil-plan-spec (10 stars, last pushed 7d ago), licensed Apache-2.0. It adds 23 tokens to every session and 443 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.
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.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
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.
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?".
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…
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…