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/tykisgod/quick-question/add-testsnpx skills add tykisgod/quick-question --skill add-testsgit clone --depth 1 https://github.com/tykisgod/quick-questionWrote 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/tykisgod/quick-question/add-tests)<a href="https://agentmods.dev/skills/tykisgod/quick-question/add-tests"><img src="https://agentmods.dev/badge/skills/tykisgod/quick-question/add-tests.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00023 | $0.01160 |
| Opus 5 | $0.00012 | $0.00580 |
| Sonnet 5 | $0.00005 | $0.00232 |
| Haiku 4.5 | $0.00002 | $0.00116 |
Grade A, and why
add-tests 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 3d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Script path fallback: qq scripts are invoked as bare commands (e.g.
unity-test.sh). If "command not found", use${CLAUDE_PLUGIN_ROOT}/bin/<command>instead.
Respond in the user's preferred language (detect from their recent messages, or fall back to the language setting in CLAUDE.md).
Add or update Unity tests for the current change. This skill is for writing tests, not for running them. After authoring coverage, hand off to /qq:test.
Querying live scene/component state while authoring tests: if you need to inspect the current Unity scene to understand what to assert (component layouts, serialized values, runtime state), see
shared/tykit-reference.md. Tools likeunity_query,unity_object,get-field,call-method,get-arraylet you probe the live editor instead of guessing from source code.
Arguments: $ARGUMENTS
- A file path, symbol, bug description, or plan step that needs coverage
editmode/edit: force EditMode coverageplaymode/play: force PlayMode coverageregression: force the smallest regression-focused test--assembly "Asm.Tests": prefer a specific test assembly--auto: skip prompts and continue into/qq:test --autoafter tests are written
0. Read qq project state first when available
If qq-project-state.py is available, read it before choosing scope:
qq-project-state.py --pretty
Use it for:
work_modeandpolicy_profileto understand expected verification pressurechanged_runtime_filesto identify the code under test when the user did not specify a targetlast_test_statusto understand whether coverage is missing vs. failing
Rules:
- Explicit user scope always wins
- Prefer the smallest meaningful coverage for the current task
- Do not turn this into a whole-project test rewrite
1. Determine the target
Pick scope in this order:
- Explicit user input (file path, bug description, plan step, or test type)
- A known failing bug / regression path from the current conversation
- The active implementation plan step and its done criteria
- Current uncommitted runtime changes
- Ask the user one concise question if the target is still ambiguous
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.
- 3d ago First seen · 115 lines · 23 tokens per session scan A c04a4e01bcc8
add-tests is a skill published in the GitHub repository tykisgod/quick-question (11 stars, last pushed 9d ago), licensed MIT. It adds 23 tokens to every session and 1,160 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-30.
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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…