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-adoptWrote 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-adopt)<a href="https://agentmods.dev/commands/alfredoperez/speckit-companion/speckit.companion.living-adopt"><img src="https://agentmods.dev/badge/commands/alfredoperez/speckit-companion/speckit.companion.living-adopt/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-adopt"><img src="https://agentmods.dev/badge/commands/alfredoperez/speckit-companion/speckit.companion.living-adopt.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.00034 | $0.04074 |
| Opus 5 | $0.00017 | $0.02037 |
| Sonnet 5 | $0.00007 | $0.00815 |
| Haiku 4.5 | $0.00003 | $0.00407 |
Grade A, and why
speckit.companion.living-adopt 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 yesterday.
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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adopt a Code Area into a Living Spec
Bring an existing code area under living specs. You point at an area. The assistant reads its surface, proposes a small tree of capabilities for just that area, drafts a living spec for each, and on your confirmation registers them so the rest of the Living Specs pipeline picks them up.
This is opt-in and incremental. It never scans or rewrites the whole repository on its own, and it changes no other command's behavior.
Reading only the surface limits what you may claim, not what you may write about. Drafts are marked [DRAFT] and low-confidence items are flagged. A requirement that restates a function signature is still not a specification. See step 2.
Input
$ARGUMENTS
The argument is the code area (or areas) to adopt: a directory (e.g. src/billing/), a small set of related files, or several directories.
If the argument is empty, do not scan the whole repo. List the plausible top-level areas, describe each in a line, and ask which to adopt. Offer adopting several at once. "All of them" is a legitimate answer.
If the argument names several areas, adopt them in one run. Propose the full tree across all of them and bring it to the single review gate in step 1. Do not expand beyond what was named.
If the argument is ., the developer asked for the whole project. Read the conventions as always, then propose the tree for the whole source tree. Say at the gate how many capabilities and how many spec files that comes to, and offer a coarser cut (one spec per area) and a finer one (a spec per concern within an area) with the count each gives. Nothing is written until they pick.
The smallest thing that works
Before building anything, stop at the first rung that holds: does it need to exist at all; does this codebase already have it; does the standard library, the platform, or an installed dependency do it; can it be one line; only then, the minimum code that works. Fix the cause where every caller passes through, not the symptom one caller reported. Delete rather than add, boring rather than clever: no interface with one implementation, no factory for one product, no scaffolding for later.
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.
- yesterday Changed f942bcaa6776
- 3d ago Changed · -9 lines 3f6593f52c51
- 6d ago Changed · +10 lines 665a5691451a
- 9d ago First seen · 183 lines · 34 tokens per session scan A 43725d7f6e03
speckit.companion.living-adopt is a command published in the GitHub repository alfredoperez/speckit-companion (90 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 4,074 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-09-03.
Other commands, from other repositories
migrate-to-typescript
Migrate JavaScript project to TypeScript.
svelte:component
Create new Svelte components with best practices, proper structure, and optional TypeScript support.
autospec.plan
Generate YAML implementation plan from feature specification.
code-locate
Given a behavior description, locate candidate code paths and line ranges in the active codebase that probably implement it. Output up to 10 candidates with HIGH/MEDIUM/LOW confidence, one-line rationale per candidate, and an explicit search trail; propose a SOURCEOFTRUTH.md update so the next workflow step (typically…
harvest-session-learnings
Scan the current working session and the active task's artifacts for reusable, generalizable lessons (what was tried, what failed and why, what surprised us, what the next task should do differently) and propose anchored entries to append to the task's LEARNINGS.md, the produce-side counterpart to the ADR-0017 consume…
screen-spec
Generate a screen specification from a Figma frame using MCP tools (getdesigncontext, getscreenshot). Produces a spec doc matching the SCREENSPEC.md template with layout sketch, components used, spacing observed, data dependencies, copy, accessibility notes, interactions, and error states. Use when documenting a…