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/ggemba/squad-mcp/questionnpx skills add ggemba/squad-mcp --skill questiongit clone --depth 1 https://github.com/ggemba/squad-mcpWrote 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/ggemba/squad-mcp/question)<a href="https://agentmods.dev/skills/ggemba/squad-mcp/question"><img src="https://agentmods.dev/badge/skills/ggemba/squad-mcp/question.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.00000 | $0.02201 |
| Opus 5 | $0.00000 | $0.01100 |
| Sonnet 5 | $0.00000 | $0.00440 |
| Haiku 4.5 | $0.00000 | $0.00220 |
Grade A, and why
question 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Question
Objective
Answer a question about the codebase. Fast, cited, read-only. Position in the workflow:
/brainstorm— decide what to build (research + options)/squad:question— answer questions about the existing code (this skill)/squad:implement— build what was decided/squad:review— review what was built
This skill exists because /squad:implement is heavy machinery (classification, plan, gates, advisors, consolidator) — overkill for "where is X?" or "what does this function do?". Question mode skips all of that and dispatches a single read-only subagent.
Inviolable Rules
- No code changes. No
Edit,Write,NotebookEditover the user's codebase. The subagent is also read-only by design — but if you, the orchestrator, are tempted to "just fix this real quick" while answering, stop. Redirect the user to/squad:implement. The only file this skill ever writes is the journal.squad/runs.jsonlviarecord_runfor telemetry — gitignored, mode0o600, not user content. Same single-writer pattern as the squad + debug skills. - No state-mutating shell or git. Read-only git (
log,show,blame,ls-files,grep,status) is fine for the subagent. The orchestrator should not invoke shell directly — let the subagent do the searching. - Cite every claim with
file:line. A statement about the code without a citation is a hallucination risk; either find the line or say "uncertain — searched X, Y, did not find". - No AI attribution in any artifact you produce.
Inputs
| Param | Default | Description |
|---|---|---|
<question> |
required | Free-form question about the code |
--quick |
off | Force breadth=quick (single grep, single excerpt). Sub-second budget. |
--thorough |
off | Force breadth=thorough (cross-cutting search, multiple stacks). Slow path. |
| (neither) | default | Breadth=medium. Up to 3 search queries, up to 5 excerpts. |
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 · 172 lines · 0 tokens per session scan A fd647a607908
question is a skill published in the GitHub repository ggemba/squad-mcp (4 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,201 tokens. 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
surf
Use when the user wants crypto data — token prices, on-chain SQL, prediction-market positions, CEX order books, wallet labels/net-worth, social mindshare, news, or unified search. 83 endpoints across exchange, on-chain, wallet, social, prediction, news and search — one API, flat $0.0085/call in USDC via x402. Settles…
video-perception
Use when the user mentions a video file (.mp4, .mov, .avi, .mkv, .webm), a YouTube URL, asks to watch/analyze/review a video, or references video content in conversation.
sanity-best-practices
Sanity development best practices for schema design, GROQ queries, TypeGen, Visual Editing, images, Portable Text, Studio structure, localization, migrations, Sanity Functions, webhooks, Blueprints, and framework integrations such as Next.js, Nuxt, Astro, Remix, SvelteKit, Angular, Hydrogen, and the App SDK. Use this…
prior-art-search
Systematic 7-step methodology for comprehensive patent prior art searches and patentability assessments using BigQuery and CPC classification.
bigquery-patent-search
Fast, cloud-based patent searching across 100 million+ worldwide patents using Google BigQuery - keyword search, CPC classification, patent details retrieval.
development-assistant
Guides through adding new features, MCP tools, analyzers, and extending the patent creator system.