Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add racecraft-lab/racecraft-plugins-public --skill speckit-upgradegit clone --depth 1 https://github.com/racecraft-lab/racecraft-plugins-publicWrote 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/skills/racecraft-lab/racecraft-plugins-public/speckit-upgrade)<a href="https://agentmods.dev/skills/racecraft-lab/racecraft-plugins-public/speckit-upgrade"><img src="https://agentmods.dev/badge/skills/racecraft-lab/racecraft-plugins-public/speckit-upgrade/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/skills/racecraft-lab/racecraft-plugins-public/speckit-upgrade"><img src="https://agentmods.dev/badge/skills/racecraft-lab/racecraft-plugins-public/speckit-upgrade.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00184 | $0.02702 |
| Opus 5 | $0.00092 | $0.01351 |
| Sonnet 5 | $0.00037 | $0.00540 |
| Haiku 4.5 | $0.00018 | $0.00270 |
Grade A, and why
speckit-upgrade 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 — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SpecKit Upgrade
Scope
Upgrade an existing SpecKit installation in the current repository
safely. Preserves .specify/memory/constitution.md and any other
locally-modified files via backup-then-force-then-restore. Supports upgrading
one or both integrations (claude, codex).
If .specify/ is missing, hands off to $speckit-install —
upgrade only operates on existing installs.
This skill is mutation-heavy (it modifies files in .specify/,
.claude/, .codex/, and writes backups to /tmp/). It runs only
on explicit operator request and never auto-fires from other
skills.
Scope Boundaries — Not For
- Initial install (no
.specify/directory yet). That is$speckit-install. This skill hands off to it automatically. - Scaffolding a new spec from the technical roadmap. That is
$speckit-scaffold-spec. - Installing this plugin's own bundled Codex subagent TOML files
into
~/.codex/agents/. That is$install. - Upgrading the SpecKit CLI binary itself (
specifypackage). The operator runs that withuv tool install --force— this skill detects when it's out of date and recommends the command, but does not run it for them.
Repository Structure Migration Guidance
For existing projects, after integration upgrade and verification, report that
repository structure migration is not available through the current runner.
The migrate-structure operation has promotion_status=deferred and no
authoritative request. Neither dry_run nor apply is an operator contract;
do not invoke the operation or claim that it will report or mutate repository
state.
Record the deferred capability gap and leave repository structure unchanged.
Tier-2 PROCESS relocation is separate, but relocate-process-artifacts is also
deferred and unavailable. Do not recommend or auto-run either operation.
Input
Accept optional integration keys as arguments:
$speckit-upgrade(upgrade all installed integrations interactively)$speckit-upgrade claude$speckit-upgrade codex$speckit-upgrade claude codex
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · -32 lines · -15 tokens per session 73845e698c06
- 7d ago First seen · 321 lines · 199 tokens per session scan A 23de6e1a5701
speckit-upgrade is a skill published in the GitHub repository racecraft-lab/racecraft-plugins-public (5 stars, last pushed today), licensed MIT. It adds 184 tokens to every session and 2,702 once invoked, about $0.0009 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-04.
Other skills, from other repositories
build-executor
Govern implementation from an approved execution contract. Invoke when execution-contract.md is approved and the user wants disciplined build work, TDD execution, or guarded batch-by-batch implementation.
workflow-start
Primary entry point for the spec-superflow state-machine workflow. Invoke when the user is inside an active spec-superflow change directory (look for .spec-superflow.yaml, changes/ /, proposal.md, specs/, design.md, tasks.md, or execution-contract.md) and asks to start, continue, resume, implement, plan, or figure out…
bug-investigator
Use when encountering any bug, test failure, or unexpected behavior during spec-superflow execution, before proposing fixes. Invoked automatically when build-executor hits a blockage.
release-archivist
Close out a spec-superflow change with verification, summary, and archive readiness. Invoke when implementation is complete, verification is underway, or the user asks for a final wrap-up.
contract-builder
Convert approved planning artifacts into an execution contract. Invoke when the user wants to start building, asks to move from planning to implementation, or when execution-contract.md is missing or stale.
spec-writer
Create or refine spec-superflow planning artifacts. Invoke when the change is understood well enough to write proposal.md, specs/, design.md, and tasks.md.