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-plan-prior-artgit 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-plan-prior-art)<a href="https://agentmods.dev/skills/hani-q/qstack/qstack-plan-prior-art"><img src="https://agentmods.dev/badge/skills/hani-q/qstack/qstack-plan-prior-art/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-plan-prior-art"><img src="https://agentmods.dev/badge/skills/hani-q/qstack/qstack-plan-prior-art.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.00158 | $0.04302 |
| Opus 5.5 | $0.00063 | $0.01721 |
| Sonnet 5.5 | $0.00032 | $0.00860 |
| Haiku 4.5 | $0.00016 | $0.00430 |
Grade A, and why
qstack-plan-prior-art 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 1mo 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 — 327 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/qstack-plan-prior-art
Read the plans this project already wrote, then brief the plan about to be written. The corpus holds decisions that were made, work that was postponed on purpose, and execution records saying what the work actually cost.
This runs on its own, because the moment it helps is the moment nobody remembers to ask for it.
Read-only
Writes nothing into the plan folder. Never edits a plan, never appends to
board-events.js, never commits. The output is a brief in the response plus one
block the planner pastes into the new plan.
The brief is derived: delete it and a second run reproduces it. The durable part is the citations that land in the new plan's research-basis sheet. So keep the brief short and get the references exactly right.
The boundary with /qstack-reflect
/qstack-reflect counts. It reads across every worktree Git tracks, reports
numbers a reader can reproduce, and refuses to interpret them. A plan folder is
a file count there, never a source of meaning.
This skill reads the plan text and interprets it, for one purpose: informing the plan about to be written. That single purpose is what permits the interpretation. Do not widen it into a project health report, and do not fold the two skills together. Reflect stays mechanical, this one stays narrow.
Arguments
/qstack-plan-prior-art [plan-dir ...]
Every argument is a directory holding plans, relative to the repository root or
absolute. Supplied paths are authoritative: read those and skip discovery. This
is the escape hatch for a project whose plans live in docs/, in rfcs/, or
outside the repository.
The subject comes from the conversation rather than the arguments. It is the
feature the user is about to plan. When /qstack-plan-to-html is the caller,
it is whichever source that skill resolved, either the Markdown draft or the
plan summary the user just confirmed. When it is not clear, state what you took
it to be in the brief's first line, so a wrong guess is visible before anything
is read.
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.
- 1mo ago Changed 6978bab4a985
- 1mo ago Changed · +43 lines · +10 tokens per session 581c81a9bbb1
- 1mo ago First seen · 284 lines · 148 tokens per session scan A 4d8828b4482a
qstack-plan-prior-art is a skill published in the GitHub repository hani-q/qstack (7 stars, last pushed 3d ago), licensed MIT. It adds 158 tokens to every session and 4,302 once invoked, about $0.0006 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…