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-plan-adherence-reviewnpx skills add hani-q/qstack --skill qstack-plan-adherence-reviewgit 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.00106 | $0.02058 |
| Opus 5 | $0.00053 | $0.01029 |
| Sonnet 5 | $0.00021 | $0.00412 |
| Haiku 4.5 | $0.00011 | $0.00206 |
Grade A, and why
qstack-plan-adherence-review 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/qstack-plan-adherence-review
Audit the implementation against the plan. Treat the plan as the contract, the code and test results as ground truth, and the execution record as supporting evidence that must itself be checked.
This is report-only work. Do not edit the plan, execution record, code, tests,
or repository instructions. Do not commit or push. Write an
adherence-review.md only when the user explicitly asks for a saved artifact;
otherwise report in the final response.
Resolve the evidence
- Use a plan path supplied by the user.
- Otherwise use a plan clearly referenced in the conversation.
- Otherwise inspect
qstack/compound_engineering/plans/*/plan.html, then legacycompound-engineering/plans/*/plan.htmlandplan.md. Never select.template/. Use the only plausible candidate; ask when multiple candidates remain. - In the plan directory, prefer
execution.md. Also readexecutor.mdand legacyimplementation-notes.mdwhen present; do not discard history merely because a newer filename exists. - Read
board-events.jsbeside them when it exists. Runnode --check, then skip its required format header and fold the remainingqstackBoardEvent({...});calls in file order for each card's final status, owner,refs, andfiles. Stop on broken JavaScript. Agents write the board while they work, so it has the standingexecution.mdalready has here: evidence to be checked against the code, never trusted on its own. When only the retiredboard.jsonlexists, fold its raw JSON lines without editing it. If both board files exist, report the conflict and trust neither.
Read repository instruction files and the whole authoritative plan. Record the plan status. A draft or proposed plan may be reviewed, but state that it lacked implementation authority.
Determine the implementation range before judging it. Prefer, in order:
- a base ref, reviewed fingerprint, or commit range explicitly recorded in the execution record;
- a base supplied by the user;
- the merge base with the repository's target branch, normally
origin/main; - a range reconstructed from plan history and relevant commits.
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 · 181 lines · 106 tokens per session scan A 823e6376c7ae
qstack-plan-adherence-review is a skill published in the GitHub repository hani-q/qstack (7 stars, last pushed 5d ago), licensed MIT. It adds 106 tokens to every session and 2,058 once invoked, about $0.0005 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.