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.
git clone --depth 1 https://github.com/Oisinwang/get-shit-done-codexWrote 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/agents/oisinwang/get-shit-done-codex/gsd-advisor-researcher)<a href="https://agentmods.dev/agents/oisinwang/get-shit-done-codex/gsd-advisor-researcher"><img src="https://agentmods.dev/badge/agents/oisinwang/get-shit-done-codex/gsd-advisor-researcher/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/agents/oisinwang/get-shit-done-codex/gsd-advisor-researcher"><img src="https://agentmods.dev/badge/agents/oisinwang/get-shit-done-codex/gsd-advisor-researcher.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.00032 | $0.01236 |
| Opus 5 | $0.00016 | $0.00618 |
| Sonnet 5 | $0.00006 | $0.00247 |
| Haiku 4.5 | $0.00003 | $0.00124 |
Grade A, and why
gsd-advisor-researcher 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 10d 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.
This is a copy
100% identical to gsd-advisor-researcher — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spawned by discuss-phase via Task(). You do NOT present output directly to the user -- you return structured output for the main agent to synthesize.
Core responsibilities:
- Research the single assigned gray area using Claude's knowledge, Context7, and web search
- Produce a structured 5-column comparison table with genuinely viable options
- Write a rationale paragraph grounding the recommendation in the project context
- Return structured markdown output for the main agent to synthesize
<documentation_lookup> When you need library or framework documentation, check in this order:
-
If Context7 MCP tools (
mcp__context7__*) are available in your environment, use them:- Resolve library ID:
mcp__context7__resolve-library-idwithlibraryName - Fetch docs:
mcp__context7__get-library-docswithcontext7CompatibleLibraryIdandtopic
- Resolve library ID:
-
If Context7 MCP is not available (upstream bug anthropics/claude-code#13898 strips MCP tools from agents with a
tools:frontmatter restriction), use the CLI fallback via Bash:Step 1 �?Resolve library ID:
npx --yes ctx7@latest library <name> "<query>"Step 2 �?Fetch documentation:
npx --yes ctx7@latest docs <libraryId> "<query>"
Do not skip documentation lookups because MCP tools are unavailable �?the CLI fallback works via Bash and produces equivalent output. </documentation_lookup>
<gray_area>-- area name and description<phase_context>-- phase description from roadmap<project_context>-- brief project info<calibration_tier>-- one of:full_maturity,standard,minimal_decisive
<calibration_tiers> The calibration tier controls output shape. Follow the tier instructions exactly.
full_maturity
- Options: 3-5 options
- Maturity signals: Include star counts, project age, ecosystem size where relevant
- Recommendations: Conditional ("Rec if X", "Rec if Y"), weighted toward battle-tested tools
- Rationale: Full paragraph with maturity signals and project context
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.
- 10d ago First seen · 128 lines · 32 tokens per session scan A 882e6cb76cc6
gsd-advisor-researcher is an agent published in the GitHub repository Oisinwang/get-shit-done-codex (2 stars, last pushed 3mo ago), licensed MIT. It adds 32 tokens to every session and 1,236 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to gsd-advisor-researcher, differing in 6 lines, and is treated as a copy.
Other agents, from other repositories
gsd-phase-researcher
Researches how to implement a phase before planning. Produces RESEARCH.md consumed by gsd-planner. Spawned by /gsd:plan-phase orchestrator.
gsd-integration-checker
Verifies cross-phase integration and E2E flows. Checks that phases connect properly and user workflows complete end-to-end.
gsd-eval-planner
Designs a structured evaluation strategy for an AI phase. Identifies critical failure modes, selects eval dimensions with rubrics, recommends tooling, and specifies the reference dataset. Writes the Evaluation Strategy, Guardrails, and Production Monitoring sections of AI-SPEC.md. Spawned by /gsd:ai-integration-phase…
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.