Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add tykisgod/quick-question/plugin install qqWrote 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/changes)<a href="https://agentmods.dev/skills/tykisgod/quick-question/changes"><img src="https://agentmods.dev/badge/skills/tykisgod/quick-question/changes/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/tykisgod/quick-question/changes"><img src="https://agentmods.dev/badge/skills/tykisgod/quick-question/changes.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00012 | $0.00416 |
| Opus 5.5 | $0.00005 | $0.00166 |
| Sonnet 5.5 | $0.00002 | $0.00083 |
| Haiku 4.5 | $0.00001 | $0.00042 |
Grade A, and why
changes 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 9d 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
Run qq scripts as
${CLAUDE_PLUGIN_ROOT}/bin/<name>: they are not on PATH, so a bareqq-run-record.pyexits 127.
Respond in the user's preferred language (detect from their recent messages, or fall back to the language setting in CLAUDE.md).
Behavior
Identify all file changes actually executed by Claude in this conversation (via Edit/Write/Bash tools) and summarize them grouped by logic.
The data source is the conversation context, not git diff — include every round, committed or not.
After producing the summary, if qq-run-record.py is available, persist a changes run record so controller state can advance:
qq-run-record.py record \
--project . \
--stage changes \
--command qq:changes \
--status checked \
--summary "Conversation change summary captured" \
--capture-local-changes
Output format
## Summary of changes in this conversation
### <Group 1 title>
- What was done
- Key files: ...
### <Group 2 title>
- ...
### Status
- Committed: <list of commit hashes, if any>
- Uncommitted: <list of files, if any>
- Compilation: passed / not verified
- Tests: N/N passed / not run
Notes
- List the main file paths for each group (omit the
Assets/Scripts/prefix to save space) - If there are architectural changes (file moves, namespace changes, asmdef changes), call them out separately
.metafiles do not need to be mentioned- If there were multiple rounds of changes in the conversation (e.g., did A first, then changed B), group them in chronological order
- If any changes were rolled back or overwritten, show only the final state, but note "tried X then changed to Y"
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.
- 9d ago Changed · -4 lines db353311a3ae
- 1mo ago First seen · 57 lines · 12 tokens per session scan A 10f1a4e6b32a
changes is a skill published in the GitHub repository tykisgod/quick-question (12 stars, last pushed 2d ago), licensed MIT. It adds 12 tokens to every session and 416 once invoked, about $0.0000 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-30.
Other skills, from other repositories
gemini
Cross-model second opinion from Google Gemini — a different AI reviewing the same changes, with deep Google ecosystem knowledge. Three modes: review (pass/fail gate for Google Ads campaigns, SEO metadata, or code), challenge (adversarial stress-test that tries to break your changes), and consult (open Q&A with Gemini…
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
boundaries
Analyze Phoenix context boundaries and module coupling via mix xref. Use when checking cross-context calls, validating dependencies, before splitting modules, or reviewing architecture.
triage
Triage review findings interactively — approve, skip, or prioritize each issue. Use after /phx:review to filter findings before fixing.
pr-threads-address
Address PR review feedback by systematically working through every unresolved PR review thread on the current branch's PR - analyze each comment, make the requested code changes (with tests where useful), commit, and optionally reply and resolve.
han-release
Cut a Han release: update CHANGELOG.md with the changes since the last release, bump and tag every plugin that changed as {plugin-name}--v{version} so a version-constrained dependency can resolve, and publish a GitHub release crediting every merged pull request and closed issue to the people behind it. Use when…