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-installgit 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-install)<a href="https://agentmods.dev/skills/racecraft-lab/racecraft-plugins-public/speckit-install"><img src="https://agentmods.dev/badge/skills/racecraft-lab/racecraft-plugins-public/speckit-install/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-install"><img src="https://agentmods.dev/badge/skills/racecraft-lab/racecraft-plugins-public/speckit-install.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 126 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00188 | $0.02294 |
| Opus 5 | $0.00094 | $0.01147 |
| Sonnet 5 | $0.00038 | $0.00459 |
| Haiku 4.5 | $0.00019 | $0.00229 |
Grade A, and why
speckit-install 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 today.
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 — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SpecKit Install
Scope
Install the official SpecKit CLI (https://github.com/github/spec-kit)
if missing, then initialize the current repository for one or both
coding-agent integrations (Claude Code, Codex CLI). Safe to run on
any repo — detects an existing .specify/ directory and hands off
to $speckit-upgrade rather than mutating it.
This skill is mutation-heavy (it writes files to the repo and
to ~/.local/share/uv/tools/specify-cli/ if installing the CLI).
It runs only on explicit operator request and never auto-fires from
other skills.
Scope Boundaries — Not For
- Upgrading an existing SpecKit install. That is
$speckit-upgrade. This skill hands off to it automatically when.specify/is present. - Scaffolding a new spec from the technical roadmap. That is
$speckit-scaffold-spec. - Installing this plugin's own bundled Codex subagent TOML files
(
autopilot-fast-helper.toml,phase-executor.toml, etc.) into~/.codex/agents/. That is$install. - Methodology coaching. That is
$speckit-coach.
Input
Accept optional integration keys as arguments:
$speckit-install(interactive — asks which integrations)$speckit-install claude$speckit-install codex$speckit-install claude codex(dual-integration)
If the operator does not specify, ask before proceeding.
Hard Constraints
- Never run
specify init --here --forcefrom this skill.--forceoverwrites local customizations. Force-flagged behavior lives exclusively in$speckit-upgrade(where it is wrapped with backup/restore). - Never mutate
.specify/memory/constitution.md. The placeholder written byspecify initis the operator's content from that moment on. - Never partially-install. If any
specifyinvocation fails, STOP and report the exact error. - Never proceed to mutation without explicit confirmation of the integration choice when there is ambiguity.
- Never touch
.claude-plugin/,commands/, or this plugin's marketplace files. Those are this plugin's own files, not the consumer repo's.
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.
- today Changed · -34 lines ca52481ae5ba
- 6d ago First seen · 280 lines · 188 tokens per session scan A 5b4a2a51c207
speckit-install is a skill published in the GitHub repository racecraft-lab/racecraft-plugins-public (5 stars, last pushed today), licensed MIT. It adds 188 tokens to every session and 2,294 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…
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.
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.
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.