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 bostonaholic/team --skill team-questiongit clone --depth 1 https://github.com/bostonaholic/teamWrote 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/bostonaholic/team/team-question)<a href="https://agentmods.dev/skills/bostonaholic/team/team-question"><img src="https://agentmods.dev/badge/skills/bostonaholic/team/team-question/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/bostonaholic/team/team-question"><img src="https://agentmods.dev/badge/skills/bostonaholic/team/team-question.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.00014 | $0.00899 |
| Opus 5.5 | $0.00006 | $0.00360 |
| Sonnet 5.5 | $0.00003 | $0.00180 |
| Haiku 4.5 | $0.00001 | $0.00090 |
Grade A, and why
team-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 2d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Before each dispatch or retry, read host dispatch and supply its resolved installed paths. Before artifact work, read artifact schema. Before handling external values, read external-data rules.
Team Question
Before finalizing prose you author, read the writing standards.
Run the QUESTION phase only, then stop. The phase writes, in docs/plans/<id>/:
1-task.md— the human's full intent. Never read byresearcherorfile-finder.2-questions.md— neutral research questions without intent; the only fileresearcherandfile-finderread.3-prd.md— only under## Conditional PRDinskills/team/playbooks/question.md.4-repos.md— only when the topic spans more than one repository: each involved repo's slug, absolute path, and role.
Execution
-
Resolve
$ARGUMENTSto a description:- Empty: discover, do not demand. Read recent
git logactivity and the repo'sREADME/CLAUDE.mdto propose a likely topic; useAskUserQuestionwith labeled options only for a genuine gap in intent. Never bare-stop with a "describe it" demand when context is available. - Ticket-only: ask the user for context, or fetch the issue body through a configured tracker integration.
- Issue URL: run
gh issue view <url> --json title,body(or equivalent) and use the title plus body as the description. - Free text: use directly.
A ticket identifier (e.g.
ENG-1234) is recorded asticketIdin1-task.mdfrontmatter. The orchestrator calls no ticketing system. - Empty: discover, do not demand. Read recent
-
Choose
<kebab-topic>: a 2–4 word kebab-case slug derived from the description. Resolve<team-question-skill-dir>to the absolute directory containing thisSKILL.md. From the repository root, run"<team-question-skill-dir>/scripts/prepare-plan-dir.sh" [--ticket <TICKET>] <kebab-topic>, passing--ticketonly when a ticket identifier is present. Itsdir=line isdocs/plans/<id>/. -
Handle its exit code. Exit 2: fix the topic or ticket its stderr names and rerun. Exit 1 or 3: stop and report its stderr.
-
Resume detection from its
state=line:new: the questioner writes every artifact.questions-only: re-read1-task.mdinstead of overwriting it; the questioner only writes2-questions.md.complete: skip dispatch and go to the report.
-
Dispatch the
questioneragent with the full description and the target directorydocs/plans/<id>/. It writes the artifacts above. -
Stop once the rerun reports
state=complete: rerun the step 2 command with--date <date>from its firstdate=line. Do not continue to RESEARCH. Any other state means the questioner did not write1-task.mdand2-questions.md; report that and stop.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago Changed · +1 lines · -7 tokens per session e6918dde5b05
- 27d ago Changed · -40 lines 8aebca3d4ac7
- 1mo ago Changed · -6 tokens per session 0539d5385253
- 1mo ago Changed · -5 tokens per session d8b0ef1ee91e
- 1mo ago Changed · -1 lines 51b7074105ea
- 1mo ago Changed · +5 lines 092201e67c5f
- 1mo ago Changed · +3 lines e6cd057220fb
- 1mo ago Changed · -4 lines · -14 tokens per session 6cc794c2aa92
- 1mo ago First seen · 105 lines · 46 tokens per session scan A d3c3a03b0633
team-question is a skill published in the GitHub repository bostonaholic/team (11 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 899 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-09-03.
Other skills, from other repositories
gsd-tools
Central utility skill for GSD operations. Provides config parsing, slug generation, timestamps, path operations, and orchestrates calls to other specialized skills. Acts as the unified entry point that the original gsd-tools.cjs provided via its lib/ modules (commands, config, core, init).
babysit-babysitter-issues
This skill should be used when the user asks to "babysit issues", "work on assigned issues", "check a5c-agent issues", "process babysitter issues", or wants to find and work on open GitHub issues assigned to a5c-agent in the babysitter repo.
spec-driven-development
Specification creation and management for the Pilot Shell methodology. Covers semantic search, clarifying questions, structured spec generation, and iterative refinement.
cog-meeting-processing
Process meeting recordings and transcripts into decisions, action items, and team dynamics.
cog-onboarding
Personalize COG Second Brain workflow through role pack selection and vault initialization.
cog-team-intelligence
Cross-reference GitHub, Linear, Slack, and PostHog with bidirectional sync for team briefs.