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/capitalone/context-specs/implement-slicenpx skills add capitalone/context-specs --skill implement-slicegit clone --depth 1 https://github.com/capitalone/context-specsWhat 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.00042 | $0.01070 |
| Opus 5 | $0.00021 | $0.00535 |
| Sonnet 5 | $0.00008 | $0.00214 |
| Haiku 4.5 | $0.00004 | $0.00107 |
Grade A, and why
implement-slice 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Slice
Executes a single slice with unit tests and a post-implementation Reflect step. Agent-first: invoked by the slice-implementer subagent under the parent orchestrator (implement-mainspec). No human prompts.
Invocation Contract
This skill is invoked by the slice-implementer subagent, not directly by the harness dispatcher. The subagent's prompt provides:
Inputs:
slice_path— absolute path to the slice file (may be outside the working directory).working_directory— absolute path to the feature branch checkout (repo root).
Outputs (uncommitted, in the working directory):
- Implemented code matching the slice's specification.
- Unit tests created/updated.
- Optional: edits under
.claude/skills/expert/references/if Reflect produced a high-bar update.
The parent orchestrator (implement-mainspec) handles git (add, commit, push) after this skill exits. Do NOT commit, do NOT run git operations, do NOT create PRs.
Result reporting (to the calling subagent):
- SUCCESS: list key files changed, tests passing, Reflect outcome (no-op | add | edit | delete).
- FAILURE: describe what went wrong. Reasons include:
test_failure(unit tests red),implementation_blocked(spec contradicts the codebase).
Workflow
- Read slice - Load the entire slice file into context.
- Create TODO list - Three items:
{slice-name} - Implement{slice-name} - Unit Tests{slice-name} - Reflect
- Implement - Mark in_progress, implement all code specified in the slice.
- Unit tests - Create/update unit tests for the implemented functionality. All tests must pass before proceeding.
- Reflect - See the Reflection Protocol below.
- Complete - Mark all TODOs complete, stop.
The working directory is the feature branch checkout. There should be no prior partial state to resume from — work as if the slate is clean.
Reflection Protocol
Run only after Implement + Unit Tests are green.
Step A — Load long-term memory
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 · 99 lines · 42 tokens per session scan A 2d87b03fcc3c
implement-slice is a skill published in the GitHub repository capitalone/context-specs (41 stars, last pushed 8d ago), licensed Apache-2.0. It adds 42 tokens to every session and 1,070 once invoked, about $0.0002 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…