Borrowing it
Nothing to install: this file belongs to alfredoperez/speckit-companion. 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/alfredoperez/speckit-companion/main/.claude/commands/publish-both.mdgit clone --depth 1 https://github.com/alfredoperez/speckit-companionWrote 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/publish-both)<a href="https://agentmods.dev/commands/alfredoperez/speckit-companion/publish-both"><img src="https://agentmods.dev/badge/commands/alfredoperez/speckit-companion/publish-both/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/publish-both"><img src="https://agentmods.dev/badge/commands/alfredoperez/speckit-companion/publish-both.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.00016 | $0.00769 |
| Opus 5 | $0.00008 | $0.00385 |
| Sonnet 5 | $0.00003 | $0.00154 |
| Haiku 4.5 | $0.00002 | $0.00077 |
Grade A, and why
publish-both 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 11d 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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
- Git status: !
git status --porcelain | head - Current branch: !
git branch --show-current - VS Code ext version: !
node -p "require('./package.json').version" - spec-kit ext version: !
grep -A4 '^extension:' speckit-extension/extension.yml | grep 'version:' | tr -d ' "' | sed 's/version://' - Latest
v*tags: !git tag --list 'v*' --sort=-version:refname | grep -v speckit-ext | head -3 - Latest
speckit-ext-v*tags: !git tag --list 'speckit-ext-v*' --sort=-version:refname | head -3
Your task
Release both extensions in one pass by running the two existing flows sequentially. This command adds orchestration only — the per-extension steps live in their own commands and stay the single source of truth:
- Phase 1 (VS Code extension):
.claude/commands/publish.md - Phase 2 (spec-kit extension):
.claude/commands/publish-speckit-ext.md
Steps
- Preflight — abort with a clear message if either fails:
- Working tree must be clean (
git status --porcelainempty). - Branch must be
main.
- Working tree must be clean (
- Ask for both target versions up front in a single question, showing both current versions. Do not ask again inside the phases.
- Phase 1 — VS Code extension. Read
.claude/commands/publish.mdand execute its task section exactly, using the version from step 2 instead of prompting. Ends with thevX.Y.Ztag pushed andrelease.ymlhandling Marketplace/OpenVSX. - Checkpoint. Confirm
release.ymlstarted for the newv*tag (gh run list --workflow=release.yml --limit 2). If Phase 1 failed at any point, stop here — do not start Phase 2 on a half-released state. - Phase 2 — spec-kit extension. Read
.claude/commands/publish-speckit-ext.mdand execute it exactly, using the version from step 2 instead of prompting. Ends with thespeckit-ext-vX.Y.ZGitHub release cut and the scratch-dir install verified. - No rollback. If Phase 2 fails, the VS Code release stays in flight (it's already on the Marketplace pipeline). Report precisely what completed, what failed, and what remains — the user finishes Phase 2 later with
/publish-speckit-ext. - Final report. Both tags, the
release.ymlrun status, the spec-kit release URL, and thespecify extension add companion --from <url>install command.
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.
- 11d ago First seen · 38 lines · 16 tokens per session scan A b625316acd4a
publish-both is a command published in the GitHub repository alfredoperez/speckit-companion (90 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 769 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-08-30.
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…