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 capitalone/context-specs --skill spec-validategit clone --depth 1 https://github.com/capitalone/context-specsWrote 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/capitalone/context-specs/spec-validate)<a href="https://agentmods.dev/skills/capitalone/context-specs/spec-validate"><img src="https://agentmods.dev/badge/skills/capitalone/context-specs/spec-validate/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/capitalone/context-specs/spec-validate"><img src="https://agentmods.dev/badge/skills/capitalone/context-specs/spec-validate.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.00064 | $0.02426 |
| Opus 5.5 | $0.00026 | $0.00970 |
| Sonnet 5.5 | $0.00013 | $0.00485 |
| Haiku 4.5 | $0.00006 | $0.00243 |
Grade B, and why
spec-validate scanned grade B 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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
1. **Discover Available Experts** — Use `ls .claude/skills/ | grep expert` (do not use Glob, as it may not resolve symlinks). How it starts
The opening of the file, as written. The whole thing — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Validate
Validate a mainspec and its slices using parallel foreground subagents for high-confidence issue detection, then apply the impactful findings as fixes directly to the spec files. Agent-first: no human-in-the-loop. Invoked headless by the harness dispatcher, walks the consensus → classify → fix → sentinel protocol, and exits.
Invocation Contract
Invoked by the dispatcher as: claude -p "/spec-validate <feature>", run from inside the feature worktree (the dispatcher cds into it — there is no print-mode --cwd flag).
Single argument: <feature> — kebab-case feature slug.
Inputs read from disk (paths relative to cwd):
specs/<feature>/mainspec.mdspecs/<feature>/slices/*.md- The codebase (subagents ground findings in actual code).
Outputs to disk:
- Edits to
specs/<feature>/mainspec.mdand/orspecs/<feature>/slices/*.mdfor impactful findings. specs/<feature>/validation-log.md— audit trail: all consensus findings, classification (impactful vs. nitpick), and which fixes were applied. For observability; not load-bearing for the dispatcher.specs/<feature>/.validated(empty sentinel).
Completion protocol (in order):
- Run 3-subagent consensus + expert review (Phases 1–2 below).
- Classify each 3/3 and 2/3 finding as impactful or nitpick (Phase 3).
- For each impactful finding: edit the affected mainspec or slice file in place.
- Write
specs/<feature>/validation-log.mdcapturing every finding, classification, and what was changed. git addall changes (edited spec files + validation-log.md), commit, push.touch specs/<feature>/.validated.git addthe sentinel, commit, push.
The sentinel is the final commit-and-push action. The dispatcher uses only the sentinel to advance to implementation.
Idempotency:
- If
specs/<feature>/.validatedalready exists, exit immediately. - If
specs/<feature>/mainspec.mddoes not exist, exit silently — the dispatcher's state machine should not have fired this skill yet; planning has not completed. - If validation-log.md exists but the sentinel does not (crash mid-write), the dispatcher's worktree wipe will discard any uncommitted log changes, so we re-run validation from scratch. Acceptable cost.
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 · 252 lines · 64 tokens per session scan B efc8c261e7d8
spec-validate is a skill published in the GitHub repository capitalone/context-specs (44 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 64 tokens to every session and 2,426 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 1 finding (enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…