Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/alfredoperez/speckit-companionnpx agentmods add commands/alfredoperez/speckit-companion/speckit.companion.living-moveWrote 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/commands/alfredoperez/speckit-companion/speckit.companion.living-move)<a href="https://agentmods.dev/commands/alfredoperez/speckit-companion/speckit.companion.living-move"><img src="https://agentmods.dev/badge/commands/alfredoperez/speckit-companion/speckit.companion.living-move/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/commands/alfredoperez/speckit-companion/speckit.companion.living-move"><img src="https://agentmods.dev/badge/commands/alfredoperez/speckit-companion/speckit.companion.living-move.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.00024 | $0.01083 |
| Opus 5.5 | $0.00010 | $0.00433 |
| Sonnet 5.5 | $0.00005 | $0.00217 |
| Haiku 4.5 | $0.00002 | $0.00108 |
Grade A, and why
speckit.companion.living-move 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 1mo 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Relocate a Living Spec
Move a capability's living spec between the two storage layouts, without hand-editing config or moving files yourself.
- central —
capabilities/<capability>/<name>.spec.md. One folder per capability, holding one spec or several granular ones. A legacycapabilities/<name>/spec.mdstill reads, and moving it centrally renames it to the new shape. - colocated —
<area root>/<name>.spec.md, sitting next to the code it describes.
Neither is more correct. Colocating makes ownership obvious and the spec travels with the code when it moves; centralizing keeps the whole record readable in one place and survives code being reorganized. Repos commonly end up mixed, and that is a fine outcome.
The move is reversible and loses nothing. A requirement's identity is its ### heading text inside the spec, so nothing outside the file points at its location — there is no id to renumber, no link to fix, no index to rebuild.
Input
$ARGUMENTS
The argument names what to move and where — a capability name and a target layout (billing to colocated), or a repo-wide instruction (everything to central).
If either is missing, ask. List the capabilities with their current layout so the developer can see what they are choosing between, and never guess at a target layout.
What to do
1. Show what will move, and pause
Resolve the current layout of each named capability and the exact path each spec will land at. Show that before touching anything:
billing capabilities/billing/billing.spec.md → src/billing/billing.spec.md
billing-tax capabilities/billing/tax.spec.md → src/billing/tax/billing-tax.spec.md
Add one line only where something would surprise them: a display name that changes (colocated names come from the file stem), a capability that stays central because its globs cover several folders or the whole area, and any .rules.md or .coverage.md that travels with the spec.
Then ask. One question, one word back. This is the only pause.
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.
- 1mo ago Changed · -4 lines aea2fc186d9c
- 1mo ago First seen · 88 lines · 24 tokens per session scan A a9ef5d78890e
speckit.companion.living-move is a command published in the GitHub repository alfredoperez/speckit-companion (99 stars, last pushed 8d ago), licensed MIT. It adds 24 tokens to every session and 1,083 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-09-03.
Other commands, from other repositories
peachflow:create-sprint
Find unlocked tasks in the current quarter, create a new sprint with up to 10 tasks, and set up a git worktree for implementation. Starts the sprint workflow.
peachflow:implement
Execute implementation of the current sprint's tasks. Works within a sprint worktree, plans approach, implements tasks in order, and tracks progress in the graph. Uses plan mode for each task.
peachflow:discover
Start product discovery for new projects OR add new features/initiatives to existing projects. Creates BRD/PRD and populates epics in the graph.
peachflow:plan
Break down epics into user stories and tasks using Claude's native plan mode. Explores context, writes plan for approval, then creates work items.
peachflow:graph
Launch a local visualization server to view the project's work item graph. Shows epics, user stories, tasks, and their relationships in an interactive browser-based interface.
peachflow:migrate
Migrate a peachflow v2 project to v3 format. Converts sprint/task files to graph structure.