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 agentmods add skills/hani-q/qstack/qstack-hownpx skills add hani-q/qstack --skill qstack-howgit clone --depth 1 https://github.com/hani-q/qstackWhat 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 | $0.00043 | $0.00541 |
| Opus 5 | $0.00022 | $0.00270 |
| Sonnet 5 | $0.00009 | $0.00108 |
| Haiku 4.5 | $0.00004 | $0.00054 |
Grade A, and why
qstack-how 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 yesterday.
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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QStack how
Build a working mental model from the code. This skill is read-only. It does not edit files, fix critique findings, commit, push, publish, deploy, or message anyone.
Choose the mode
- Explain is the default. Answer how the system works and where behavior lives.
- Critique runs only when the user asks for architectural problems or improvements. Explain the system first, then critique it.
This skill explains mechanism, placement, and ownership. Label inferred motivation as inference instead of presenting it as historical fact.
Investigate
- Resolve the subject and scope. For harmless ambiguity, state a reasonable interpretation and proceed. Ask only when different interpretations would materially change the answer.
- Search for the entry point and read the implementation. Trace callers, callees, state changes, data transformations, types, and boundaries until the path from trigger to effect has no hand-waved step.
- Check repository instructions, configuration, generated code, tests, and external boundaries that change the flow. Do not infer behavior from names.
- Record exact paths, symbols, and lines. State any path that could not be traced.
Handle a narrow question directly. For a cross-cutting subsystem, read complex exploration. When the answer needs a full onboarding narrative, read structured explanation.
Present
Lead with the direct answer. Then include only the concepts, flow, file map, and gotchas needed to make it understandable. Use a diagram when it materially clarifies several components or state transitions.
For Critique mode, read architecture critique only after the explanation is grounded in the code. Report findings and tradeoffs; do not apply fixes.
Adapted from Lauren Tan's PStack
how
at commit 60c641e4fad674784b30abcf9f8915dea39df38d under the MIT License.
See third-party notices.
What ships with it
4 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.
- yesterday First seen · 57 lines · 43 tokens per session scan A 17b43f62837c
qstack-how is a skill published in the GitHub repository hani-q/qstack (7 stars, last pushed 5d ago), licensed MIT. It adds 43 tokens to every session and 541 once invoked, about $0.0002 per session on Opus 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
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…