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.after-implementWrote 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.after-implement)<a href="https://agentmods.dev/commands/alfredoperez/speckit-companion/speckit.companion.after-implement"><img src="https://agentmods.dev/badge/commands/alfredoperez/speckit-companion/speckit.companion.after-implement/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.after-implement"><img src="https://agentmods.dev/badge/commands/alfredoperez/speckit-companion/speckit.companion.after-implement.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.00020 | $0.00527 |
| Opus 5 | $0.00010 | $0.00264 |
| Sonnet 5 | $0.00004 | $0.00105 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
speckit.companion.after-implement 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 8d 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Capture Implement Context
Record the active feature's implementation progress into .spec-context.json so the
SpecKit Companion GUI re-renders with the correct step and status. This command
runs as the after_implement lifecycle hook. It uses the writer's TASK-SYNC mode: it reads the completed task markers in the feature's tasks.md and appends one transition per completed task (idempotent — already-recorded tasks are skipped), ending at status=implemented when every marker is checked, otherwise status=implementing.
Prerequisites
- Verify Python is available by running
python3 --version. - If
python3is not available, warn the user and skip the capture:[companion] Warning: python3 not detected; skipped .spec-context.json capture. Do not fail the host command.
Execution
Run the writer script from the repository root, passing the active feature's tasks.md path:
python3 .specify/extensions/companion/scripts/write-context.py --step implement --status implemented --by extension --tasks-file specs/<NNN>-<slug>/tasks.md
Pass the active feature's tasks.md path to --tasks-file. If feature resolution is unambiguous the script resolves the feature directory on its own (in this order: --feature-dir → SPECIFY_FEATURE_DIRECTORY env → SPECIFY_FEATURE env → .specify/feature.json → current git branch prefix), but --tasks-file must still point at that feature's tasks.md. The --status implemented value is the terminal status applied only when all task markers are checked; partial completion records implementing automatically.
Graceful Degradation
The script is best-effort and never fails the host command:
- If
python3is missing, skip with the warning above. - If the active feature directory cannot be resolved, the script prints a warning to stderr and exits 0 without writing.
Output
On success the script prints the path it updated and the values written, e.g.:
[companion] Updated specs/<NNN>-<slug>/.spec-context.json (currentStep=implement, status=implementing, by=extension).
The write is atomic (temp file + rename) and appends to the canonical history[] without
rewriting existing entries.
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.
- 8d ago First seen · 41 lines · 20 tokens per session scan A 77620d62f40b
speckit.companion.after-implement is a command published in the GitHub repository alfredoperez/speckit-companion (90 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 527 once invoked, about $0.0001 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
camp-init
Create a new camp with the standard directory structure. A camp was previously called a campaign; camp init is the same command either way.
fest-list
List all festivals with their status and completion percentage.
fest-next
Get the next actionable festival task with full context.
sddp-implement-qc-loop
Command description: Run implement and QC in a continuous loop. Argument hint: [optional: feature directory or branch name] Command category: orchestration Prerequisites: spec, plan, tasks.
sddp-amend
Command description: Propagate a bootstrap change across canonical project artifacts and the project plan. Argument hint: [project-level change to propagate across bootstrap artifacts] Command category: project-bootstrap Prerequisites: project-instructions, product-document, technical-context, project-plan.
sddp-clarify
Command description: Reduce ambiguity in the current feature specification. Argument hint: [optional: ambiguity focus or feature directory] Command category: feature-delivery Prerequisites: spec.