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 tykisgod/quick-question --skill briefgit 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/brief)<a href="https://agentmods.dev/skills/tykisgod/quick-question/brief"><img src="https://agentmods.dev/badge/skills/tykisgod/quick-question/brief/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/brief"><img src="https://agentmods.dev/badge/skills/tykisgod/quick-question/brief.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.00022 | $0.01018 |
| Opus 5.5 | $0.00009 | $0.00407 |
| Sonnet 5.5 | $0.00004 | $0.00204 |
| Haiku 4.5 | $0.00002 | $0.00102 |
Grade A, and why
brief 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 13d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Respond in the user's preferred language (detect from their recent messages, or fall back to the language setting in CLAUDE.md).
Arguments: $ARGUMENTS
- No arguments: compare against the default base branch (develop if it exists, else main, else master)
--base <branch>: specify a custom base branch for comparison--commits: only look at the changes from the most recent commit
Execution Steps
Part 1: Collect Change Scope
git diff <base>...HEAD --name-only | grep '\.cs$'— get all changed C# filesgit diff <base>...HEAD --diff-filter=A --name-only | grep '\.cs$'— get newly added filesgit log <base>..HEAD --oneline— get the commit list- Group and count changes by module
- Use
git diff <base>...HEAD --numstatto get accurate added/deleted line counts per module
Part 2: Architecture Change Diagram
Identify architectural changes, ordered from most to least significant:
Tier 1 — Cross-module contract changes
- Interface additions/modifications under Contracts/
- .asmdef dependency changes
- Public enum/data structure changes
- Global static state isolation in multi-instance scenarios
Tier 2 — New modules/subsystems
- New Service modules or subdirectories
- New Manager/Factory/Registry classes
- New state machines or process orchestration
Tier 3 — Internal refactoring of existing modules
- Initialization flow changes
- Pattern changes such as singleton → dependency injection
- Data flow direction changes
Tier 4 — Extension points/configuration changes
- New interface implementations
- Config structure changes
- New events/callbacks
Draw at least one Mermaid diagram for every architectural change:
- Module dependency changes →
graph LR, color-coded: new (green) / modified (orange) / deleted (red) - Data flow / lifecycle →
sequenceDiagramorflowchart - State machines →
stateDiagram-v2 - Class relationships →
classDiagram
Diagram requirements:
- Each diagram has a title indicating "Before vs After"
- Use
styleor:::to annotate added and modified nodes - No more than 15 nodes per diagram
- Stable, unchanged modules use gray/dashed styling
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.
- 13d ago Changed · -5 lines · +2 tokens per session 4d29d3c71c60
- 1mo ago First seen · 144 lines · 20 tokens per session scan A 0cf786cce1d8
brief is a skill published in the GitHub repository tykisgod/quick-question (12 stars, last pushed 3d ago), licensed MIT. It adds 22 tokens to every session and 1,018 once invoked, about $0.0001 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
pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
phx-pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
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…
han-update-documentation
Update Han plugin documentation so every skill, agent, guidance doc, index, and cross-reference is current and accurate. On a non-default branch, scopes the pass to entities the branch actually touched. On the default branch, performs a full documentation sweep across the whole plugin. Use when updating, refreshing…
up-to-date
Preflight sync and situational brief before repo work: fetches origin, reports ahead/behind divergence (with a no-upstream/detached-HEAD fallback), recent commits, open PRs and issues touching the work, and dirty-tree warnings, then names one recommended first action. Read-only by default — never pulls, rebases…