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-be-concisenpx skills add hani-q/qstack --skill qstack-be-concisegit 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.00065 | $0.00413 |
| Opus 5 | $0.00032 | $0.00206 |
| Sonnet 5 | $0.00013 | $0.00083 |
| Haiku 4.5 | $0.00006 | $0.00041 |
Grade A, and why
qstack-be-concise 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.
What it actually says
/qstack-be-concise
Rewrite the immediately previous assistant answer. Output only the rewrite.
Choose the length
- If the invocation includes a positive whole number
N, useNorN + 1short lines. For example,/qstack-be-concise 4produces about 4–5 lines. - Otherwise, count the non-empty lines in the previous answer and use this guide:
- 1–5 lines: rewrite in 1–2 lines.
- 6–12 lines: rewrite in 2–3 lines.
- 13–24 lines: rewrite in 3–5 lines.
- 25–49 lines: rewrite in 5–7 lines.
- 50 or more lines: rewrite in 7–10 lines.
- Treat the ranges as ceilings, not quotas. Use fewer lines when they are enough.
- Exceed a requested limit only when needed to avoid an unsafe or seriously misleading answer.
Rewrite rules
- Preserve the important result, decisions, warnings, and next action.
- Use everyday words a non-technical reader can understand.
- Remove jargon, implementation details, file paths, command names, and process narration unless the user must know them to act.
- Translate any unavoidable technical term immediately into plain language.
- Do not add new facts, repeat the work, call tools, or change the meaning.
- Prefer one short sentence per line. Avoid headings, tables, code blocks, preambles, apologies, and commentary about shortening the answer.
- If there is no previous substantive assistant answer, say so in one short line.
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.
- yesterday First seen · 35 lines · 65 tokens per session scan A 6be4285750b9
qstack-be-concise is a skill published in the GitHub repository hani-q/qstack (7 stars, last pushed 5d ago), licensed MIT. It adds 65 tokens to every session and 413 once invoked, about $0.0003 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…