pob-mcp: Command for Claude Code

.claude/commands/agent-os/write-spec.md

write-spec is a command for Claude Code from ianderse/pob-mcp. It costs 0 tokens per session (158 once invoked), scanned A, original, GPL-3.0.

A command for creating a detailed specification for a new software feature. A specification records what should be built and the conditions for considering it complete.

In plain words
What is it for?
Use it when planning a new feature and need a written scope, requirements, and completion criteria.
Why use it?
Starting implementation without clear requirements can lead to missing work or mismatched expectations. This command creates a shared reference before coding begins.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is ianderse/pob-mcp's own configuration. It tells Claude Code how to work on pob-mcp 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 pob-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ianderse/pob-mcp. 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/ianderse/pob-mcp/main/.claude/commands/agent-os/write-spec.md
Clone the repo
git clone --depth 1 https://github.com/ianderse/pob-mcp

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 write-spec

README.md
[![agentmods](https://agentmods.dev/badge/commands/ianderse/pob-mcp/write-spec/github.svg)](https://agentmods.dev/commands/ianderse/pob-mcp/write-spec)
Your own site
<a href="https://agentmods.dev/commands/ianderse/pob-mcp/write-spec"><img src="https://agentmods.dev/badge/commands/ianderse/pob-mcp/write-spec/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 write-spec

Your own site · 80×15
<a href="https://agentmods.dev/commands/ianderse/pob-mcp/write-spec"><img src="https://agentmods.dev/badge/commands/ianderse/pob-mcp/write-spec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 158 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 unknown 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.00000 $0.00158
Opus 5.5 $0.00000 $0.00063
Sonnet 5.5 $0.00000 $0.00032
Haiku 4.5 $0.00000 $0.00016

Measured 2mo ago against content hash 0cca23e9a619, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

write-spec 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 2mo 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/commands/agent-os/write-spec.md · 23 lines

The source is not reproduced here

Licensed GPL-3.0

The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

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. 2mo ago First seen · 23 lines · 0 tokens per session scan A 0cca23e9a619

Subscribe to this mod's changes

write-spec is a command published in the GitHub repository ianderse/pob-mcp (50 stars, last pushed 2d ago), licensed GPL-3.0. It costs nothing until one of its globs matches a file; then it loads 158 tokens. 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.

Related

write-spec compared with commands from other repositories

write-spec next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
write-specianderse/pob-mcpCommand502d agoGPL-3.0A0Claude Code
checklistgithub/spec-kitCommand148kyesterdayMITA13Claude Code
clarifygithub/spec-kitCommand148kyesterdayMITA27Claude Code
specifygithub/spec-kitCommand148kyesterdayMITA13Claude Code
analyzegithub/spec-kitCommand148kyesterdayMITA26Claude Code
convergegithub/spec-kitCommand148kyesterdayMITA35Claude Code
implementgithub/spec-kitCommand148kyesterdayMITA14Claude Code