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/leefowlercu/agent-kit/project-specs-reconciliationnpx skills add leefowlercu/agent-kit --skill project-specs-reconciliationgit clone --depth 1 https://github.com/leefowlercu/agent-kitWhat 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.00099 | $0.01933 |
| Opus 5 | $0.00049 | $0.00966 |
| Sonnet 5 | $0.00020 | $0.00387 |
| Haiku 4.5 | $0.00010 | $0.00193 |
Grade A, and why
project-specs-reconciliation 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 3d 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 — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Specs Reconciliation
Use this skill to turn a requested project change into durable project documentation before implementation begins. Create or update PRDs for product behavior and ADRs for architectural decisions.
Do not implement application code under this skill. End with a handoff for project-specs-implementation or another local BDD/TDD implementation workflow.
Composition With Implementation
Use this skill for the governance red phase: establish or repair the PRD, ADR, matrix, and implementation handoff before production-code changes. Use project-specs-implementation for the implementation red, green, refactor, and verification phases after this skill produces a complete handoff.
If implementation work exposes missing or contradictory requirements, return to this skill before continuing code changes.
Template Assets
Use these bundled templates when creating new specifications:
assets/prd-template.md
assets/adr-template.md
Copy the relevant template, replace the number and title, and fill every section with project-specific content. Do not leave template placeholder prose in generated PRDs or ADRs.
Conventional Locations
Use these locations without broad discovery:
docs/PRD/
docs/ADR/
When the user provides an explicit scope, use:
docs/<scope>/PRD/
docs/<scope>/ADR/
Use these conventional files when present or needed:
docs/PRD/README.md
docs/PRD/MATRIX.md
docs/ADR/README.md
For scoped projects, place the same files below docs/<scope>/PRD/ and docs/<scope>/ADR/.
Do not infer alternate spec locations by searching the repository. If the expected conventional directory is absent, create it when a new PRD or ADR is needed.
Stage 1: Classify Intent
Step 1: Restate the requested change
Restate the user's intent as a concise behavior or decision statement.
Step 2: Choose PRD, ADR, or both
Use a PRD when the change affects:
- externally observable behavior
- user workflows
- product requirements
- CLI, API, UI, or integration outcomes
- acceptance criteria
- behavioral compatibility
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 281 lines · 99 tokens per session scan A e023fceef638
project-specs-reconciliation is a skill published in the GitHub repository leefowlercu/agent-kit (6 stars, last pushed 1mo ago), licensed MIT. It adds 99 tokens to every session and 1,933 once invoked, about $0.0005 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…