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 agentmods add skills/rhtevan/agentfs/spec-kit-setupnpx skills add rhtevan/agentfs --skill spec-kit-setupgit clone --depth 1 https://github.com/rhtevan/agentfsWhat 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 | $0.00016 | $0.00845 |
| Opus 5 | $0.00008 | $0.00423 |
| Sonnet 5 | $0.00003 | $0.00169 |
| Haiku 4.5 | $0.00002 | $0.00085 |
Grade A, and why
spec-kit-setup 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 2d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec-kit Setup
Detect, install, or upgrade the specify CLI (GitHub Spec Kit) via uv tool.
What This Skill Does
- Locates
uv(checks PATH,~/.hermes/bin,~/.local/bin,~/.cargo/bin, nix store). - Checks whether
specifyis already installed and reads its current version. - Fetches the latest release tag from
github.com/github/spec-kit/releases/latest. - Compares the installed version against the latest tag.
- Installs (fresh) or upgrades (if behind or
--force) usinguv tool install specify-cli --force --from git+...@<tag>. - Verifies the new installation by running
specify version.
Usage
Run the bundled script from the skill directory:
bash <skill-dir>/scripts/check-and-install.sh
Options
| Flag | Effect |
|---|---|
--json |
Machine-readable JSON output |
--force |
Reinstall even if already at the latest version |
--tag vX.Y.Z |
Pin to a specific release tag instead of latest |
Examples
# Auto-detect and install/upgrade to latest
bash <skill-dir>/scripts/check-and-install.sh
# Force reinstall at current latest
bash <skill-dir>/scripts/check-and-install.sh --force
# Pin to a specific release
bash <skill-dir>/scripts/check-and-install.sh --tag v0.11.8
# JSON output for scripted use
bash <skill-dir>/scripts/check-and-install.sh --json
Prerequisites
- uv — must be installed and locatable (the script searches common paths)
- Python 3.11+ — required by the specify CLI
- Git — required by
uv tool installto clone the spec-kit repo - Network access — to reach
api.github.comandgithub.com
If uv is not found, install it first: https://docs.astral.sh/uv/
Version Detection
Spec-kit has shipped two different specify version output formats:
| Format | CLI Version Field | Release Version Source |
|---|---|---|
| Old (CLI ≤ 0.0.x) | CLI Version + Template Version |
Template Version matches the release tag |
| New (CLI ≥ 0.11.x) | CLI Version only |
CLI Version matches the release tag |
What ships with it
2 files 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.
- 2d ago First seen · 120 lines · 16 tokens per session scan A 6cf1f11c074b
spec-kit-setup is a skill published in the GitHub repository rhtevan/agentfs (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 16 tokens to every session and 845 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…