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-nextgit 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-next)<a href="https://agentmods.dev/skills/hani-q/qstack/qstack-next"><img src="https://agentmods.dev/badge/skills/hani-q/qstack/qstack-next/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-next"><img src="https://agentmods.dev/badge/skills/hani-q/qstack/qstack-next.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.00063 | $0.00931 |
| Opus 5.5 | $0.00025 | $0.00372 |
| Sonnet 5.5 | $0.00013 | $0.00186 |
| Haiku 4.5 | $0.00006 | $0.00093 |
Grade B, and why
qstack-next scanned grade B with 1 finding 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 23d 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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
The listing script in `/qstack` prints them; `ls ~/.claude/skills How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/qstack-next
Say what was just done, what that leaves undone, and the one skill that closes the gap. Three or four lines. Name the skill; never run it.
Evidence, heaviest first
- The plan folder. Files on disk say where the work is more reliably than the conversation does. See the table below.
- The working tree.
git branch --show-current,git status --short,git log --oneline -5. Uncommitted changes mean work that is not yet verified or reviewed. - The conversation. What the user asked last, what was produced, what was verified. Facts, not tone: "it's broken" followed by three guards and no reproduction is evidence; a frustrated message is not.
Read what you need and no more. This skill is read-only.
The plan lifecycle
Plan folders are qstack/compound_engineering/plans/<slug>/, or the legacy
compound-engineering/plans/<slug>/. The folder whose slug matches the branch
or the conversation is the one that matters. Its files arrive in a fixed
order, and the first one missing is the next step:
| The folder has | Run next |
|---|---|
| Nothing yet, and the user is describing a feature or change | /qstack-plan-prior-art, then draft plan.md |
plan.md and no plan.html |
/qstack-plan-to-html |
plan.html with notes at data-status="open" |
/qstack-ask-plan-open-questions |
plan.html and no board-events.js, or a board without its complete-breakdown marker |
/qstack-plan-to-html to finish the board |
board-events.js with cards still open |
the execution loop execution.md shows was used; /qstack-loop-no-nonsense when it shows none |
every card closed and no outcome.md, on a board with no review epic |
/qstack-plan-adherence-review, then /qstack-plan-close |
every card closed and no outcome.md, on a board whose review epic gate card is done |
/qstack-plan-close; the gate card already ran the adherence review |
outcome.md |
nothing from the lifecycle |
Work with no plan folder and no feature being described is outside the lifecycle; do not push it in.
What ships with it
1 file 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.
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.
- 23d ago Changed · -1 lines a9f1f724e04c
- 1mo ago Changed · +1 lines 9061480663f6
- 2mo ago First seen · 84 lines · 63 tokens per session scan B 090d2e4874f7
qstack-next is a skill published in the GitHub repository hani-q/qstack (7 stars, last pushed 3d ago), licensed MIT. It adds 63 tokens to every session and 931 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 1 finding (enumerates other installed skills). 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…