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 qstackgit 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)<a href="https://agentmods.dev/skills/hani-q/qstack/qstack"><img src="https://agentmods.dev/badge/skills/hani-q/qstack/qstack/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"><img src="https://agentmods.dev/badge/skills/hani-q/qstack/qstack.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00065 | $0.00715 |
| Opus 5.5 | $0.00026 | $0.00286 |
| Sonnet 5.5 | $0.00013 | $0.00143 |
| Haiku 4.5 | $0.00006 | $0.00072 |
Grade A, and why
qstack 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 22d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/qstack
Show what is installed, then what to run next. Nothing is stored here: every run reads the skills on disk at that moment, so a skill added or a collection installed yesterday appears today.
1. Read the installed skills
Run scripts/installed-skills, next to this file, once. It prints one row per
skill as collection<TAB>name<TAB>path<TAB>description.
What the script decides, so you do not have to:
- A skill belongs to QStack when its directory is
qstackor starts withqstack-. That is the naming contractinstalland skills.sh both keep. human-reviewis its own collection.- Any other skill is included only when the skills.sh lock file records it as
installed from one of the collections QStack's installer offers, and the
copy found is the one that entry describes. The script reads the lock where
that CLI writes it, honouring
XDG_STATE_HOME, and itsCOLLECTIONSmap is the one list of those sources. - Skills from collections QStack does not install (gstack, greptile, ...) are left out. They have their own routers.
- A skill linked into more than one harness directory is listed once.
If the script prints nothing, say that no QStack skills were found under
~/.claude/skills, ~/.codex/skills, or ~/.agents/skills, and stop.
2. Render the tables
Condense each description to one line:
- Keep the first sentence. Drop any "Use when ...", "Use for ...", or "Triggers on ..." clause; that text is for the model, not the reader.
- About twelve words at most, starting with a verb, no trailing full stop.
- Say only what the description says. Do not add detail it lacks.
- Keep the order the script printed.
Output exactly this, and nothing before it:
## qstack
| Skill | What it does |
| --- | --- |
| /qstack-plan-prior-art | ... |
## Installed with qstack
| Skill | Collection | What it does |
| --- | --- | --- |
| /human-review | human-review | ... |
| /ask-matt | Matt Pocock | ... |
Write each skill as /name. Omit the second table when the script printed no
rows outside qstack. No preamble, no install advice, no remarks about skills
that are absent.
What ships with it
2 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.
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.
- 22d ago Changed · -53 lines · -8 tokens per session e5e3456c71c1
- 2mo ago First seen · 133 lines · 73 tokens per session scan A fcf2404485d1
qstack is a skill published in the GitHub repository hani-q/qstack (7 stars, last pushed 3d ago), licensed MIT. It adds 65 tokens to every session and 715 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…