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-core-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-core-html)<a href="https://agentmods.dev/skills/ngvoicu/kluris/specmint-core-html"><img src="https://agentmods.dev/badge/skills/ngvoicu/kluris/specmint-core-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-core-html"><img src="https://agentmods.dev/badge/skills/ngvoicu/kluris/specmint-core-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.00152 | $0.10405 |
| Opus 5.5 | $0.00061 | $0.04162 |
| Sonnet 5.5 | $0.00030 | $0.02081 |
| Haiku 4.5 | $0.00015 | $0.01040 |
Grade A, and why
specmint-core-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 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 — 912 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Mint Core HTML
Turn ephemeral plans into structured, persistent specs built through deep
research and iterative interviews. Specs render as professional HTML
documents — Mermaid diagrams, syntax-highlighted code diffs, UI mockups
(wireframe and hi-fi), status pills, derived progress dashboards — and
live in .specs/ at the project root. They work with any AI coding tool
that can read and edit HTML files.
Whether .specs/ is committed is repository policy. Respect .gitignore
and the user's preference for tracked vs local-only spec state.
Critical Invariants
- Single-file policy: Keep this workflow in one
SKILL.mdfile. - Canonical paths:
- Registry:
.specs/registry.md(markdown, denormalized index) - Shared assets:
.specs/assets/spec-styles.css+.specs/assets/spec-runtime.js - Per-spec files:
.specs/<id>/SPEC.html,.specs/<id>/research-*.md,.specs/<id>/interview-*.md - Optional scratch:
.specs/<id>/artifacts/— any AI-tool transient files (test-run logs, attempt dumps, debug traces). Never authoritative. Don't write scratch files anywhere else under.specs/<id>/.
- Registry:
- Authority rule: The
<script id="spec-meta">JSON insideSPEC.htmlis authoritative for identity. Thedata-statusattributes on tasks / phases / acceptance criteria are authoritative for lifecycle. The registry is a denormalized index for quick lookup. - Active-spec rule: Target exactly one active spec at a time.
- Parser policy: Use best-effort parsing with clear warnings and repair guidance instead of hard failure on malformed rows.
- Progress tracking is sacred: After completing any task, immediately
update
SPEC.html(data-statusswap and any phase transition) ANDregistry.md(progress count, date). Run the validate recipe (seereferences/validate.md) to confirm the file still parses. Re-read both files to verify the edits landed. Never move to the next task without updating both files. Never end a session with the registry out of sync with the derived progress inSPEC.html. This is non-negotiable.
What ships with it
10 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.
- assets/spec-runtime.js 35 KB runs code
- assets/spec-styles.css 50 KB
- references/command-contracts.md 5.8 KB
- references/edit-recipes.md 12 KB
- references/html-template.html 10 KB
- references/mockup-library.md 9.8 KB
- references/researcher.md 11 KB
- references/spec-format.md 12 KB
- references/validate.md 5.7 KB
- references/wireframe-library.md 9.4 KB
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 Changed · +683 lines · +86 tokens per session d1f1a4f860e4
- 1mo ago First seen · 229 lines · 66 tokens per session scan A 65c893150beb
specmint-core-html is a skill published in the GitHub repository ngvoicu/kluris (6 stars, last pushed today), licensed MIT. It adds 152 tokens to every session and 10,405 once invoked, about $0.0006 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
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
review-finished-ad
Final QC gate for a rendered 9:16 video ad, run before it is published. One script checks what a machine can decide — exact 1080x1920 size, a hook that moves and speaks in the first second, no frozen stretches, no dead air, no black frames, the brand's real logo on the end card (never a favicon, never a redrawn or…
review-work
Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.
render-3d-character-explainer
Assemble an animated character-explainer video ad (77s, 9:16, any art style: Pixar-style 3D, claymation, anime, paper-cut, felt) on an "N types of X" listicle spine: one recurring human protagonist plus one persona character per list item. Given per-scene clips, a scene timing table and narration, it trims…
ad-policy-check
Checks paid ads against the ad platform's rules (Meta, TikTok, Google, LinkedIn and others) and the brand's category rules: the copy, on-image or on-screen text, pictures and people. Rewrites what can be fixed honestly, adds the disclosures that are needed, and flags anything that needs a human or legal review, with…