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-explain-forgit 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-explain-for)<a href="https://agentmods.dev/skills/hani-q/qstack/qstack-explain-for"><img src="https://agentmods.dev/badge/skills/hani-q/qstack/qstack-explain-for/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-explain-for"><img src="https://agentmods.dev/badge/skills/hani-q/qstack/qstack-explain-for.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.00118 | $0.00944 |
| Opus 5.5 | $0.00047 | $0.00378 |
| Sonnet 5.5 | $0.00024 | $0.00189 |
| Haiku 4.5 | $0.00012 | $0.00094 |
Grade A, and why
qstack-explain-for 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 26d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/qstack-explain-for
Rewrite the immediately previous assistant answer for the reader named in the invocation. Output only the rewrite.
Read the invocation
The argument is free text. Take the reader's role from it and, when present, the product that reader owns. All of these are valid:
/qstack-explain-for(product manager, product inferred)/qstack-explain-for ceo/qstack-explain-for pm dpi/qstack-explain-for cmo of a fitness app/qstack-explain-for a new support engineer on the habit tracker
Defaults:
- No role: product manager.
- No product: the product this repository or conversation builds. If nothing identifies one, frame the rewrite around users and outcomes without naming a product.
The product is whatever the reader owns. When it matches what the codebase builds, speak in that product's real features. When it does not, map each technical concept onto that product's nearest feature or user outcome, and name the mapping the first time it appears so the reader can translate back.
Choose the lens
Each role sets what the reader is accountable for and the question they are silently asking. Answer that question first.
| Role | Accountable for | Silent question | Keep | Drop |
|---|---|---|---|---|
| Product manager | User outcomes, scope, priority | What changes for users, what does it cost us, what is the tradeoff? | Behavior change, affected users, scope, options, decisions still open | Implementation mechanics, file paths, internal names |
| CEO or founder | Business risk, time, money | Are we exposed, what does it delay, what does it cost? | Risk, delay, cost, decision needed, the one number that matters | Everything below the outcome |
| CMO or marketing | Positioning, claims, launch | What can we say, what must we not say, when? | What is true now, what is coming, caveats on claims | Mechanism, architecture, code |
| CTO or engineering manager | Delivery, quality, team load | How big is it, what could go wrong, who is blocked? | Effort, risk, dependencies, sequencing, what is unverified | Line-level detail, command output |
| Sales or customer success | Deals, customer promises | Can I promise this, to whom, and when? | Customer-visible behavior, limits, timing, workarounds | Internals of any kind |
| Support | Tickets, diagnosis | How do I recognize it, what do I tell the customer? | Symptoms, who is affected, workaround, fix status | Root-cause code detail beyond recognition |
| Anything else | Infer from the role | Infer what this person answers for, then answer that | Whatever moves their decision | Whatever does not |
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.
- 26d ago Changed · +16 tokens per session e3e62ae311bd
- 1mo ago First seen · 67 lines · 102 tokens per session scan A 4fd2f5a220f4
qstack-explain-for is a skill published in the GitHub repository hani-q/qstack (7 stars, last pushed 3d ago), licensed MIT. It adds 118 tokens to every session and 944 once invoked, about $0.0005 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-09-05.
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…