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-quality-check)<a href="https://agentmods.dev/skills/shrekshrek/project-workflow/spec-quality-check"><img src="https://agentmods.dev/badge/skills/shrekshrek/project-workflow/spec-quality-check.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.00042 | $0.00262 |
| Opus 5 | $0.00021 | $0.00131 |
| Sonnet 5 | $0.00008 | $0.00052 |
| Haiku 4.5 | $0.00004 | $0.00026 |
Grade A, and why
spec-quality-check 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.
What it actually says
Spec Quality Check
Match the user's language. Read ${CLAUDE_PLUGIN_ROOT}/docs/actions/spec-quality-check.md completely before reviewing. Use the canonical semantic method in the current conversation; an applicable independent reviewer reads its own role contract.
Claude execution details:
- Resolve
$ARGUMENTSusing the shared active-feature rules; excludearchive/. Read the actual record and relevant optional attachments. - Perform the canonical readiness and requirements-reconciliation checks. Read the relevant method from
${CLAUDE_PLUGIN_ROOT}/docs/reviewers/spec-quality-reviewer.mdfor this semantic work. - Only when the canonical independent-review boundary applies, dispatch a fresh
spec-quality-reviewerwith the necessary decision sources and affected record under the shared execution contract. - Apply the canonical verdict, status, and implementation-handoff rules; never repair artifact content or commit. Report the canonical reconciliation and verdict compactly, plus blocking findings, any status transition, and the next action. Do not add an adapter-specific report schema or narrate every ordinary pass.
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 First seen · 20 lines · 42 tokens per session scan A 474ec4fe09d6
spec-quality-check is a skill published in the GitHub repository shrekshrek/project-workflow (2 stars, last pushed 2d ago), licensed MIT. It adds 42 tokens to every session and 262 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-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.
review
5-pass structured code review — correctness, security, performance, readability, consistency.
marshal
Meta-orchestrator that takes any direction — broad, specific, or vague — and autonomously chains skills and context into actionable work. Gathers context from codebase, docs, and memory. Only asks the user when it genuinely cannot proceed. Single-session orchestrator.
systematic-debugging
4-phase root cause analysis: observe, hypothesize, verify, fix. Enforces investigation before any code changes. Emergency stop after 2 failed fixes. Prevents shotgun debugging and fix cascades.
qiongli
Qiongli version: v1.17.0. Cross-platform academic research workflow for Codex, Claude / Claude Code, and CLI. Use for academic research lifecycle work: paper planning, literature review, paper reading, gap finding, study design, manuscript writing, statistics, analysis code, reproducibility, proofread, rebuttal…