Borrowing it
Nothing to install: this file belongs to lbruton/claude-context. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/lbruton/claude-context/master/.agents/skills/spec-reconcile/SKILL.mdgit clone --depth 1 https://github.com/lbruton/claude-contextWrote 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/lbruton/claude-context/spec-reconcile)<a href="https://agentmods.dev/skills/lbruton/claude-context/spec-reconcile"><img src="https://agentmods.dev/badge/skills/lbruton/claude-context/spec-reconcile/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/lbruton/claude-context/spec-reconcile"><img src="https://agentmods.dev/badge/skills/lbruton/claude-context/spec-reconcile.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.00032 | $0.00884 |
| Opus 5.5 | $0.00013 | $0.00354 |
| Sonnet 5.5 | $0.00006 | $0.00177 |
| Haiku 4.5 | $0.00003 | $0.00088 |
Grade A, and why
spec-reconcile 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 5d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/spec-reconcile ISSUE PHASE
Bridge between /spec-review markup and a clean phase file the next phase can build on. Reads reviewer marks, classifies them, applies the accepted ones with explicit human approval, and archives the originals verbatim.
Invocation
/spec-reconcile <ISSUE-ID> <phase>
<phase> is required: requirements | discovery | approach | tasks. Missing either arg → print usage and exit.
Read first — shared conventions
Read .agents/skills/spec/references/conventions.md for folder resolution and the reviewer-mark grammar (the > AGENT: / ## {AGENT} Review / ## {AGENT} — Unverified Assumptions patterns and the ## Review Archive exclusion).
Steps
-
Resolve the spec folder; open
{phase}.md. Collect every unreconciled artifact (per the grammar in conventions.md): inline> {AGENT}:blocks,## {AGENT} Reviewsections,## {AGENT} — Unverified Assumptionssubsections. Anything under## Review Archiveis already done — ignore. If none found: "no reviewer comments found in {phase}.md — nothing to reconcile" and exit. Do not invent work. -
Classify each distinct finding by cluster — Consensus (2+ agents, match by intent not string) / Single-source / Divergent (agents disagree) — and disposition:
- Accept — correct + mechanical fix. Apply without asking.
- Reject — out of scope / already handled / factually wrong. Verify code-existence claims against the live repo before rejecting (reviewers are fallible; an unchecked reject inherits their assumption). One-sentence reason required.
- Needs-your-call — judgment, divergent cases, scope/tradeoff decisions.
-
Inline Q&A — do NOT batch. Hit a needs-your-call item → ask the moment you reach it (AskUserQuestion for clean choices, plain text otherwise), integrate the answer, continue. Batching turns each question into a re-orientation tax.
-
Print the reconcile plan — ACCEPT (n) / REJECT (n, with reasons) / YOUR-CALL resolved (n) / NET CHANGES to
{phase}.md/ ARCHIVE note. Then wait for an explicit approval signal ("approve", "go", "do it"). Generic "looks good" or silence is not approval. Adjust + re-print if asked.
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.
- 5d ago Changed 0b914edb3453
- 9d ago Changed 717e4add13e1
- 11d ago First seen · 58 lines · 32 tokens per session scan A 4b7714707c62
spec-reconcile is a skill published in the GitHub repository lbruton/claude-context (2 stars, last pushed 5d ago), licensed MIT. It adds 32 tokens to every session and 884 once invoked, about $0.0001 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-10-17.
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…
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…
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…