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-unslopnpx skills add hani-q/qstack --skill qstack-unslopgit 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.00027 | $0.01348 |
| Opus 5 | $0.00014 | $0.00674 |
| Sonnet 5 | $0.00005 | $0.00270 |
| Haiku 4.5 | $0.00003 | $0.00135 |
Grade A, and why
qstack-unslop 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 2d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/qstack-unslop
Rewrite the immediately previous assistant answer. Output only the rewrite.
Process
- Scan for the patterns below.
- Rewrite while preserving meaning, useful detail, technical accuracy, and the intended tone. Do not shorten merely for the sake of shortening.
- Add human voice where it fits.
- Ask, "What makes this obviously AI generated?" Fix the remaining tells.
Do not add facts, claims, decisions, or recommendations. Keep file paths, commands, warnings, and next actions when the reader still needs them. Do not repeat the work or call tools.
If there is no previous substantive assistant answer, say so in one short line.
Human voice
- Have opinions when judgment is useful. React to facts instead of mechanically listing pros and cons.
- Vary rhythm. Mix short sentences with longer ones when the idea needs room.
- Acknowledge real complexity instead of flattening every reaction.
- Use "I" when it fits. First person is not unprofessional.
- Allow natural asymmetry. Perfectly repeated structure looks manufactured.
- Be specific. Replace a vague feeling with the fact that causes it.
Patterns to fix
Content
- Puffery. Cut phrases such as "pivotal moment", "testament to", "evolving landscape", "setting the stage for", "indelible mark", and "deeply rooted." State what happened.
- Name-dropping. Do not list media outlets without context. Pick the relevant source and say what it reported.
- Superficial -ing phrases. Delete or substantiate phrases such as "highlighting", "ensuring", "reflecting", "showcasing", and "fostering."
- Promotional language. Replace "nestled", "vibrant", "breathtaking", "groundbreaking", "renowned", "stunning", and "must-visit" with neutral descriptions.
- Vague attributions. Name the source behind "experts believe", "industry reports suggest", or "some critics argue", or delete the claim.
- Formulaic challenges. Replace "despite challenges, it continues to thrive" with the specific facts.
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.
- 2d ago First seen · 120 lines · 27 tokens per session scan A d4ecc5d11907
qstack-unslop is a skill published in the GitHub repository hani-q/qstack (7 stars, last pushed 5d ago), licensed MIT. It adds 27 tokens to every session and 1,348 once invoked, about $0.0001 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…