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 hani-q/qstack --skill qstack-plan-to-htmlgit clone --depth 1 https://github.com/hani-q/qstackWrote 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/hani-q/qstack/qstack-plan-to-html)<a href="https://agentmods.dev/skills/hani-q/qstack/qstack-plan-to-html"><img src="https://agentmods.dev/badge/skills/hani-q/qstack/qstack-plan-to-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/hani-q/qstack/qstack-plan-to-html"><img src="https://agentmods.dev/badge/skills/hani-q/qstack/qstack-plan-to-html.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 562 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00068 | $0.07825 |
| Opus 5.5 | $0.00027 | $0.03130 |
| Sonnet 5.5 | $0.00014 | $0.01565 |
| Haiku 4.5 | $0.00007 | $0.00783 |
Grade A, and why
qstack-plan-to-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 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 — 671 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/qstack-plan-to-html
Takes a plan, from a Markdown draft or from the conversation that worked it out, and produces a controlled document: numbered, citable, offline-safe, and readable by two audiences at once.
A plan is not a landing page. It opens with a title block, every clause is numbered so a reviewer can say "§4.2 is wrong", and every section carries a status stamp so a reader knows what is settled before reading a word.
Language: plain words, always
Write it the way you would say it out loud. Jargon is not precision; most of the time it is precision's opposite, because it lets a vague sentence pass as an informed one. If a sentence would survive being read aloud to a smart person outside the team, keep it. If it would not, rewrite it.
Cut these on sight. They carry no information:
leverage · utilize · synergy · holistic · robust · seamless · paradigm · best-in-class · surface area (as a metaphor) · first-class citizen · orthogonal · non-trivial · trivially · simply · just · obviously
| Instead of | Write |
|---|---|
| "leverage the existing abstraction" | "use the code that is already there" |
| "a non-trivial refactor" | "about three days of work across four files" |
| "the system exhibits sub-optimal latency characteristics" | "it takes 40 seconds; it should take 2" |
| "we surface this to the operator" | "the operator sees it" |
| "simply add a policy rule" | "add a policy rule": if it were simple you would not be writing a plan |
Precise is not the same as jargon. A term of art that names a real thing
earns its place. A term already used in the codebase, such as first-match,
hot reload, or run-to-completion, stays, because replacing it with a vague
paraphrase loses information an implementer needs. The rule is to use the
exact word, then explain it once in an ELI10 box the first time it appears.
Numbers beat adjectives. "Fast" is an opinion; "16 ms" is a fact. Wherever the source markdown has a measurement, use the measurement.
What ships with it
24 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.
- agents/openai.yaml 262 B
- references/board-breakdown.md 19 KB
- references/board-protocol.md 41 KB
- references/model-routing.md 7.3 KB
- references/update-plan-assets.md 4.4 KB
- scripts/update-plan-assets 6.4 KB
- template/card-ref 5.3 KB
- template/migrate-board-log 2.4 KB
- template/serve.sh 2.6 KB runs code
- template/v1/board.js 55 KB runs code
- template/v1/fonts/archivo-var.woff2 34 KB
- template/v1/fonts/OFL-Archivo.txt 4.3 KB
- template/v1/fonts/OFL-IBMPlexMono.txt 4.4 KB
- template/v1/fonts/OFL-SourceSerif4.txt 4.3 KB
- template/v1/fonts/plexmono-400.woff2 9.8 KB
- template/v1/fonts/plexmono-500.woff2 9.8 KB
- template/v1/fonts/README.md 1.6 KB
- template/v1/fonts/sourceserif4-italic-var.woff2 127 KB
- template/v1/fonts/sourceserif4-var.woff2 119 KB
- template/v1/plan-template.html 9.3 KB
- template/v1/plan.css 53 KB
- template/v1/plan.js 9.8 KB runs code
- template/v1/pretext.js 30 KB runs code
- template/v1/README.md 20 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.
- 1mo ago Changed · +32 lines c945302755d2
- 1mo ago Changed · +16 lines ceff28ea7274
- 1mo ago Changed · +15 lines d646b4a04b8c
- 1mo ago First seen · 608 lines · 68 tokens per session scan A eeb88001e0b6
qstack-plan-to-html is a skill published in the GitHub repository hani-q/qstack (7 stars, last pushed 3d ago), licensed MIT. It adds 68 tokens to every session and 7,825 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…