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/schmidthole/serf/spec-checknpx skills add schmidthole/serf --skill spec-checkgit clone --depth 1 https://github.com/schmidthole/serfWhat 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.00022 | $0.00520 |
| Opus 5 | $0.00011 | $0.00260 |
| Sonnet 5 | $0.00004 | $0.00104 |
| Haiku 4.5 | $0.00002 | $0.00052 |
Grade A, and why
spec-check 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
reference
read development-workflow.md for the full conventions governing the specs directory structure, features, work items, and their formats.
instructions
check for drift between feature specs and their implementation. $ARGUMENTS is an optional feature name to check a single feature. if omitted, check all features.
follow these steps:
-
locate features. read
specs/features/features.mdto get the list of features. if a specific feature was provided, filter to just that one. -
for each feature with status
in-progressorimplemented(skip features with statusconsolidatedorretired):a. read the
spec.mdand extract the## Source Pathssection.b. if no source paths are listed, flag it as "missing source paths".
c. for each source path listed, verify it exists in the codebase using glob. flag any paths that do not exist as "stale source path".
d. read the spec's technical details (data structures, function signatures, config fields, behavior descriptions) and compare against the actual code at the source paths. flag any divergences as "spec drift".
-
check for orphaned code. look for source files that implement feature-related logic but are not listed in any feature's source paths. this is a best-effort heuristic check, not exhaustive.
-
output a report in this format:
## spec check results
### <feature-name> — <status>
- [x] source paths exist
- [ ] spec matches code — <brief description of drift>
### <feature-name> — <status>
- [ ] missing source paths
if everything is in sync, output a clean bill of health.
- offer to align. if any drift was detected, ask the user whether they would like to update the feature specs to match the current code. if approved:
- update
spec.mdto reflect the actual implementation, preserving existing structure and writing style - add or remove source paths as needed
- do not remove spec context that is still accurate
- present each proposed change before making it
- update
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 · 56 lines · 22 tokens per session scan A d33dfd69c83f
spec-check is a skill published in the GitHub repository schmidthole/serf (2 stars, last pushed 5mo ago), licensed BSD-3-Clause. It adds 22 tokens to every session and 520 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…