Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add shrekshrek/project-workflow/plugin install project-workflowWrote 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/shrekshrek/project-workflow/spec-reconcile)<a href="https://agentmods.dev/skills/shrekshrek/project-workflow/spec-reconcile"><img src="https://agentmods.dev/badge/skills/shrekshrek/project-workflow/spec-reconcile.svg" alt="Measured on agentmods" 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.00023 | $0.00249 |
| Opus 5 | $0.00012 | $0.00125 |
| Sonnet 5 | $0.00005 | $0.00050 |
| Haiku 4.5 | $0.00002 | $0.00025 |
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 6d 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.
What it actually says
Spec Reconcile
Match the user's language and preserve file language. Read ${CLAUDE_PLUGIN_ROOT}/docs/actions/spec-reconcile.md completely before acting; it owns conflict and lifecycle semantics.
Claude execution details:
- Parse
$ARGUMENTSas an area, module path, or explicit feature list; use the shared active-feature rules and excludearchive/from candidates. - Use Claude's native question/approval flow for canonical decision groups and their lifecycle/current-truth changes; present evidence and a recommendation without choosing a winner silently.
- After precedence approval, move losing artifacts with an ordinary filesystem rename and run
node "${CLAUDE_PLUGIN_ROOT}/scripts/relocate-markdown-links.cjs" <old-dir> <new-dir>after each move. If relocation fails, move the directory back before stopping; apply prepared status/current-truth edits only after successful relocation. - Do not modify implementation code, delete history, or commit.
Return the canonical verdict with the conflict matrix, applied lifecycle changes, current-truth gaps, ADR follow-ups, and next action.
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.
- 6d ago First seen · 19 lines · 23 tokens per session scan A 05d15d91f4a1
spec-reconcile is a skill published in the GitHub repository shrekshrek/project-workflow (2 stars, last pushed 3d ago), licensed MIT. It adds 23 tokens to every session and 249 once invoked, about $0.0001 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
evolve
Research-driven multi-cycle improvement director. Forms causal hypotheses about why scores are low, validates them with scout agents before attacking, dispatches axis-parallel fleet attacks, extracts transferable patterns, and runs indefinitely within a budget envelope. Accumulates a persistent belief model and…
improve
Autonomous quality improvement loop. Scores a target against a rubric, selects the highest-leverage axis, attacks it, verifies, documents, and loops. No pre-planning between iterations — each loop re-scores from scratch.
pr-watch
Local PR watcher. Monitors CI status, automatically fixes failing checks by reading failure logs and applying targeted fixes, then optionally merges when all checks pass. Local CLI analog to Claude Code's cloud auto-fix feature.
qa
Browser-based QA verification. Launches a real browser, navigates the app, clicks buttons, fills forms, and tests user flows. Works as a standalone skill or as a phase end condition in campaigns. Requires Playwright (optional dependency, graceful skip if not installed).
review
5-pass structured code review — correctness, security, performance, readability, consistency.
live-preview
Mid-build visual verification loop. Takes screenshots of components during construction, not just after. Catches visual regressions and invisible features before they compound. Requires Playwright or similar screenshot tool.