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.
git clone --depth 1 https://github.com/ronronner02/codepilot-agentWrote 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/ronronner02/codepilot-agent/spec-runtime-setup)<a href="https://agentmods.dev/commands/ronronner02/codepilot-agent/spec-runtime-setup"><img src="https://agentmods.dev/badge/commands/ronronner02/codepilot-agent/spec-runtime-setup/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/ronronner02/codepilot-agent/spec-runtime-setup"><img src="https://agentmods.dev/badge/commands/ronronner02/codepilot-agent/spec-runtime-setup.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.00017 | $0.11503 |
| Opus 5.5 | $0.00007 | $0.04601 |
| Sonnet 5.5 | $0.00003 | $0.02301 |
| Haiku 4.5 | $0.00002 | $0.01150 |
Grade C, and why
spec-runtime-setup scanned grade C with 1 finding 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 1mo 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.
Instruction-override phrasinghighPrompt injection
Text telling the model to disregard its earlier instructions or safety rules is the shape of a prompt injection, whoever wrote it.
- `Project local config`: example config, local override, gitignore safety rule, legacy markdown config signal, and retired legacy local config status. Human labels and machine fields should be de-branded; active setup f How it starts
The opening of the file, as written. The whole thing — 360 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command support root: .claude/spec-first/workflows/spec-runtime-setup. Treat it as the loaded skill directory whenever this inlined workflow refers to SKILL_DIR or the directory containing SKILL.md.
Runtime Setup
spec-runtime-setup is the canonical runnable entrypoint for the Runtime Setup workflow across supported hosts (Claude/Qoder command spelling runtime-setup). Host-specific setup spellings are not separate products. Runtime Setup prepares deterministic host/runtime facts for spec-first workflows. It installs or verifies required MCP servers and baseline helper tooling, diagnoses manual helpers such as agent-browser, writes setup-owned project facts, and reports concrete next actions. It does not provide code-understanding authority; downstream workflows use bounded direct source reads, rg, ast-grep, git diff, tests/logs, and user-provided evidence.
Contract Summary
| Field | Contract |
|---|---|
| When to use | Host runtime setup, MCP setup, helper-tool readiness, missing runtime assets, or project-local setup fact refresh. |
| When not to use | Ordinary planning, implementation, review, debugging, or code impact questions that can proceed from direct source evidence. |
| 输入 | 当前 host、repo target、已加载 skill 共置的 setup-registry.json、host config 状态、git/workspace target facts 与项目 instruction。 |
| Outputs | Readiness ledger v2, provider readiness v2 facts, generated runtime manifest freshness, setup scenario fingerprint, project-local config bootstrap status, optional project setup facts under .spec-first/config/, and a grouped status block. |
| Artifacts | .spec-first/config/tool-facts.json, .spec-first/config/runtime-capabilities.json, .spec-first/config.local.example.yaml, .spec-first/config.local.yaml when explicitly created, .gitignore local-config safety rule when explicitly ensured, and .spec-first/workspace/scenario-fingerprint-setup.json when applicable. |
| Failure modes | Missing dependencies, host config write failure, ambiguous parent workspace target, symlink escape, invalid registry schema, helper install failure, or unsupported host. |
| Downstream consumers | using-spec-first, plan/work/review/debug workflows, doctor/update guidance, and humans repairing setup. |
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.
- 1mo ago First seen · 360 lines · 17 tokens per session scan C c14d672efab5
spec-runtime-setup is a command published in the GitHub repository ronronner02/codepilot-agent (0 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 11,503 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (instruction-override phrasing). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
infogenius
Research-First Image Generation - Facts → Visual Prompt → High-Quality Image.
close-track
Close a completed track — run quality gate, update conductor state, commit, and optionally handle the git branch.
audit-plugin
Audit plugin skills, commands, and agents for structure, size, and naming issues.
release
Prepare a release (step 1 of 2) — version bump and PR. Cutting the tag is a separate operator-only step.
new-agent
Scaffold a new LangGraph agent with best practices.
just-ship-vps
VPS verwalten — Status pruefen, Projekte verbinden, neuen VPS einrichten.