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-prove-it-worksnpx skills add hani-q/qstack --skill qstack-prove-it-worksgit 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.00046 | $0.00457 |
| Opus 5 | $0.00023 | $0.00229 |
| Sonnet 5 | $0.00009 | $0.00091 |
| Haiku 4.5 | $0.00005 | $0.00046 |
Grade A, and why
qstack-prove-it-works 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.
What it actually says
Prove it works
For every completion claim, identify the direct observation that would make it true. Verification does not authorize remediation, deployment, external messages, unsafe live mutations, commits, pushes, or publishing.
Prove the real path
- State the exact claim and the artifact that owns the truth.
- Validate the observation method. When a check disagrees with the system, inspect stale caches, derived views, and faulty probes before choosing which result to trust.
- Build or validate static structure when relevant, but treat that as a prerequisite rather than proof of runtime behavior.
- Run the actual artifact and exercise the feature from input through every boundary to its output. For integrations, test the complete communication path in a safe environment.
- Read actual values and artifacts. Check process liveness directly. Inspect delegated diffs, files, and runtime results instead of accepting summaries.
- Script complex or repeatable comparisons when that makes the evidence deterministic. Keep temporary proof local unless a durable artifact was requested.
Report each claim, check, observed evidence, and result. Mark any segment that
requires unavailable infrastructure or additional authority as UNPROVEN;
do not substitute a proxy. During approved planned work, record durable evidence
in the existing QStack execution.md and create no second audit format.
Adapted from Lauren Tan's PStack
principle-prove-it-works
at commit 60c641e4fad674784b30abcf9f8915dea39df38d under the MIT License.
See third-party notices.
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 · 42 lines · 46 tokens per session scan A 610130e7cdde
qstack-prove-it-works is a skill published in the GitHub repository hani-q/qstack (7 stars, last pushed 5d ago), licensed MIT. It adds 46 tokens to every session and 457 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.
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.