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 implement-slicegit 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/implement-slice)<a href="https://agentmods.dev/skills/capitalone/context-specs/implement-slice"><img src="https://agentmods.dev/badge/skills/capitalone/context-specs/implement-slice/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/implement-slice"><img src="https://agentmods.dev/badge/skills/capitalone/context-specs/implement-slice.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 78 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00042 | $0.01070 |
| Opus 5.5 | $0.00017 | $0.00428 |
| Sonnet 5.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 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.
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.
- 1mo 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 (44 stars, last pushed 1mo 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.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
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
dart-test
DART Test: unit tests, integration tests, CI validation, and debugging.
principle-test-behavior-not-implementation
Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.
restore-internals-seams-in-finally-blocks-after-each-test
When delegating a task affected by this skill, include.