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/briefnpx 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.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.00020 | $0.01086 |
| Opus 5 | $0.00010 | $0.00543 |
| Sonnet 5 | $0.00004 | $0.00217 |
| Haiku 4.5 | $0.00002 | $0.00109 |
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 4d 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 — 144 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).
Compare the current branch against develop and generate two review documents: architecture change diagram + PR review checklist.
Arguments: $ARGUMENTS
- No arguments: compare main...HEAD
--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
- Check anti-patterns defined in AGENTS.md
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 a Mermaid diagram for each Tier:
- Module dependency changes →
graph LR, color-coded: new (green) / modified (orange) / deleted (red) - Data flow / lifecycle →
sequenceDiagramorflowchart - State machines →
stateDiagram-v2 - Class relationships →
classDiagram
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.
- 4d ago First seen · 144 lines · 20 tokens per session scan A 0cf786cce1d8
brief is a skill published in the GitHub repository tykisgod/quick-question (11 stars, last pushed 9d ago), licensed MIT. It adds 20 tokens to every session and 1,086 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
google-ads-audit
Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…
review
5-pass structured code review — correctness, security, performance, readability, consistency.
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.
codex-test-gen
Generate unit tests for specified functions using Codex MCP.
brand-docx
Brand-aware Word engine. Use to (1) EXTRACT a company's brand from a Word template into a reusable "Brand Profile", (2) COMPREHEND the template with the model (optional), (3) VERIFY it, (4) GENERATE new on-brand .docx documents FROM a saved profile. Trigger on "extract our brand", "learn/match this template", "use our…
extract-resume
Parse a resume's uploaded PDF into structured JSON (basics, experience, projects, skills, education) and save it to the editor.