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 ngvoicu/kluris --skill specmint-tdd-htmlgit clone --depth 1 https://github.com/ngvoicu/klurisWrote 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/ngvoicu/kluris/specmint-tdd-html)<a href="https://agentmods.dev/skills/ngvoicu/kluris/specmint-tdd-html"><img src="https://agentmods.dev/badge/skills/ngvoicu/kluris/specmint-tdd-html/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/ngvoicu/kluris/specmint-tdd-html"><img src="https://agentmods.dev/badge/skills/ngvoicu/kluris/specmint-tdd-html.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.00074 | $0.03253 |
| Opus 5 | $0.00037 | $0.01626 |
| Sonnet 5 | $0.00015 | $0.00651 |
| Haiku 4.5 | $0.00007 | $0.00325 |
Grade A, and why
specmint-tdd-html 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 10d 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 — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Mint TDD HTML — Kluris Companion
Turn feature requests into HTML specs and implement them with strict TDD. This
HTML variant uses .specs/<id>/SPEC.html as the canonical spec document. The
HTML file carries metadata, acceptance criteria, phases, TEST/IMPL task pairs,
data-status progress, data-tdd-phase red-green-refactor state, diagrams,
code previews, the TDD log, decisions, and deviations.
When this file is referenced from a Kluris-generated brain skill, read and
follow it directly from ~/.kluris/companions/specmint-tdd-html/SKILL.md.
Do not ask the user to install Specmint separately. Kluris vendors companions
as single SKILL.md files, so every rule needed for companion mode is below.
Critical Invariants
- Canonical files
- Registry:
.specs/registry.md(markdown index) - Per-spec document:
.specs/<id>/SPEC.html - Research notes:
.specs/<id>/research-*.md - Interview notes:
.specs/<id>/interview-*.md - Scratch, if needed:
.specs/<id>/artifacts/
- Registry:
- Authority rule: the JSON inside
<script type="application/json" id="spec-meta">is authoritative for identity and spec status.data-statusattributes on phases, tasks, and acceptance criteria are authoritative for progress.data-tdd-phaseon implementation tasks recordsred,green, orrefactorstate when a cycle is in progress. - TDD invariant: no production code without a failing test. Capture the RED failure before writing implementation, make GREEN with the smallest production change, then REFACTOR under green tests.
- HTML is the source of truth: do not create or update a parallel markdown spec for an HTML companion spec.
- Progress tracking is sacred: after completing any task, immediately
update
SPEC.html(data-status,data-tdd-phase, phase transitions, updated date, TDD log) and.specs/registry.md(progress/date). Re-read both files before moving on. - Single-file companion mode: use inline HTML/CSS/JS patterns in the
SPEC.htmlyou write. Do not rely on unavailable sibling template or asset files from a separate plugin install.
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.
- 10d ago First seen · 254 lines · 74 tokens per session scan A 901854e19124
specmint-tdd-html is a skill published in the GitHub repository ngvoicu/kluris (7 stars, last pushed 2mo ago), licensed MIT. It adds 74 tokens to every session and 3,253 once invoked, about $0.0004 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
pdlc-feature
An automated workflow for taking a new software feature from a description or requirements document through requirements, design, testing, implementation, review, and release preparation. It keeps one feature ID across the documents and requires tests before implementation.
pdlc-implement
A guarded coding workflow that implements a feature from its design document and existing tests, then checks the result. It requires tests to be written first, following TDD (test-driven development).
pdlc-tdd
A test-first development workflow guided by existing design documents. TDD means writing tests before the code they check; PDLC is a staged product-development process with required preparation steps.
pdlc-loop-run
An automated loop that moves a feature through TDD, implementation, and review. TDD, or test-driven development, means writing tests as part of defining and checking the code’s expected behavior.
aidex-bugfix
Use when fixing a bug, resolving a reported issue, or when something is broken and needs a test-driven fix — investigate root cause, write a failing regression test (RED), implement the minimum fix, confirm the test passes (GREEN), then commit test and fix together. Fires on "fix this bug", "this is broken", "it's not…
tdd
Use before writing any implementation code — enforces RED-GREEN-REFACTOR cycle.