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 hams-ollo/zen-agent-skills --skill spec-qualitygit clone --depth 1 https://github.com/hams-ollo/zen-agent-skillsWrote 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/hams-ollo/zen-agent-skills/spec-quality)<a href="https://agentmods.dev/skills/hams-ollo/zen-agent-skills/spec-quality"><img src="https://agentmods.dev/badge/skills/hams-ollo/zen-agent-skills/spec-quality/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/hams-ollo/zen-agent-skills/spec-quality"><img src="https://agentmods.dev/badge/skills/hams-ollo/zen-agent-skills/spec-quality.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.00077 | $0.02236 |
| Opus 5.5 | $0.00031 | $0.00894 |
| Sonnet 5.5 | $0.00015 | $0.00447 |
| Haiku 4.5 | $0.00008 | $0.00224 |
Grade A, and why
spec-quality 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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec quality
Adapted from repoprompt-workflows (Balarama Bosch), MIT.
Intent
Help agents draft and review specs that are contract-level, scenario-driven, testable, non-redundant, and grounded in existing repository context.
A good spec says what behavior should exist and why it matters. It does not become the implementation plan, architecture brief, task list, or test file design.
This skill is a lens, not a drafting workflow: it is meant to be composed into one. spec-author drafts specs and calls this lens to check its own output before returning it.
When to use
Use this skill when working on any scenario-based spec or spec-like draft, including:
- product or implementation specs;
Problem,Goals,Non-Goals,Constraints,Scenarios,Proposed Surface, orOpen Questionssections;- Given/When/Then scenarios;
- spec review, repair, validation, or quality checklists.
This skill can guide drafting or return a quality report. It does not replace a repo's explicit Spec workflow when that workflow is responsible for writing files, naming specs, or updating spec indexes.
Inputs
Required:
- Spec draft or source request: readable spec content, proposed spec sections, scenarios, or a user request for a future spec.
Optional:
- Repository context: existing names, tools, commands, APIs, docs, schemas, or conventions that should ground the spec wording.
If no spec draft or source request is supplied, or the supplied input cannot be interpreted as spec-related content, report input_error and do not return ready.
Non-goals
Do not use this skill to:
- replace an explicit Spec workflow that writes spec files (for example under a repo's
docs/spec/convention) or updates spec indexes; - write spec files (e.g. under
docs/spec/) unless the user explicitly asks for file edits; - update a spec index such as
docs/spec/README.md; - create implementation plans, architecture documents, code, or tests;
- decide feature implementation details that belong to planning or design;
- judge readiness of a Spec plus Deep Plan pair; use a dedicated
spec-plan-readinessprocess for that. - judge whether an implementation conforms to a spec (spec-vs-implementation); use
spec-conformancefor that, ordoc-syncfor doc-vs-code drift.
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 Changed · +7 lines ab370e01c2e8
- 2mo ago First seen · 219 lines · 77 tokens per session scan A 9cd3fec4c836
spec-quality is a skill published in the GitHub repository hams-ollo/zen-agent-skills (2 stars, last pushed 7d ago), licensed MIT. It adds 77 tokens to every session and 2,236 once invoked, about $0.0003 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-31.
Other skills, from other repositories
review
Use when explicitly invoked to review a branch diff (or any diff or files pointed at) with a find-only subagent covering rubric and conventions, change conformance against the AC-N and their runtime-verification evidence, and documentation consistency — one plain-text verdict that reaches lgtm only when no dimension…
implement
Use when explicitly invoked to execute a change's tasks.md from the first unticked step: implement each task, run its validation, commit, then run the quality gate and verify every acceptance criterion by observed behavior. Needs no conversation context — the change folder is the whole input. Trigger on…
archive
Use when explicitly invoked to close out a change whose branch has already merged: confirm the merge from git alone, then move the change folder under changes/archive/ with its ship date. Trigger on '/sw:archive', '$sw:archive', 'archive this change', or a request to close out a merged change.
ship
Use when explicitly invoked to run the whole change ladder without stopping — ticket, plan, implementation, quality gate, runtime verification, review to lgtm — deciding every open question autonomously and recording each decision in proposal.md. Trigger on '/sw:ship', '$sw:ship', or a request to take something from…
gsd-audit-milestone
Audit milestone completion against original intent before archiving.
spec-kitty-charter-doctrine
Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter"…