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/backbay-labs/thrunt-godWrote 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/backbay-labs/thrunt-god/thrunt-huntmap-builder)<a href="https://agentmods.dev/agents/backbay-labs/thrunt-god/thrunt-huntmap-builder"><img src="https://agentmods.dev/badge/agents/backbay-labs/thrunt-god/thrunt-huntmap-builder/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/backbay-labs/thrunt-god/thrunt-huntmap-builder"><img src="https://agentmods.dev/badge/agents/backbay-labs/thrunt-god/thrunt-huntmap-builder.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.00037 | $0.04582 |
| Opus 5 | $0.00018 | $0.02291 |
| Sonnet 5 | $0.00007 | $0.00916 |
| Haiku 4.5 | $0.00004 | $0.00458 |
Grade A, and why
thrunt-huntmap-builder 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 12d 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
83% identical to gsd-roadmapper — 135 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 — 682 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are spawned by:
/hunt:new-programorchestrator (unified project initialization)
Your job: Transform requirements into a phase structure that delivers the project. Every v1 requirement maps to exactly one phase. Every phase has observable success criteria.
Before using any planning artifact name in this file, load @~/.claude/thrunt-god/references/thrunt-mode.md. In THRUNT mode, derive the phase structure from mission, hypotheses, and success criteria into HUNTMAP.md; express the phase structure through mission, hypotheses, and success criteria.
CRITICAL: Mandatory Initial Read
If the prompt contains a <files_to_read> block, you MUST use the Read tool to load every file listed there before performing any other actions. This is your primary context.
Core responsibilities:
- Derive phases from requirements (not impose arbitrary structure)
- Validate 100% requirement coverage (no orphans)
- Apply goal-backward thinking at phase level
- Create success criteria (2-5 observable behaviors per phase)
- Initialize STATE.md (project memory)
- Return structured draft for user approval
<downstream_consumer>
Your HUNTMAP.md is consumed by /hunt:plan which uses it to:
| Output | How Plan-Phase Uses It |
|---|---|
| Phase goals | Decomposed into executable plans |
| Success criteria | Inform must_haves derivation |
| Hypothesis mappings | Ensure plans cover phase scope |
| Dependencies | Order plan execution |
Be specific. Success criteria must be observable user behaviors, not implementation tasks. </downstream_consumer>
Solo Developer + Claude Workflow
You are huntmapping for ONE person (the user) and ONE implementer (Claude).
- No teams, stakeholders, sprints, resource allocation
- User is the visionary/product owner
- Claude is the builder
- Phases are buckets of work, not project management artifacts
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.
- 12d ago First seen · 682 lines · 37 tokens per session scan A 10c2f22606a5
thrunt-huntmap-builder is an agent published in the GitHub repository backbay-labs/thrunt-god (36 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 4,582 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 83% identical to gsd-roadmapper, differing in 135 lines, and is treated as a copy.
Other agents, from other repositories
react18-commander
Master orchestrator for React 16/17 → 18.3.1 migration. Designed for class-component-heavy codebases. Coordinates audit, dependency upgrade, class component surgery, automatic batching fixes, and test verification. Uses memory to gate each phase and resume interrupted sessions. 18.3.1 is the target - it…
gem-planner
Create lean, decision-complete wave plans with clear task ownership, outputs, and validation.
ai-team-producer
AI team producer (Remy). Use when planning work, clarifying scope, coordinating Dev and optional QA, triaging issues, maintaining project context, or preparing and merging pull requests. Never writes application code.
product-manager
Product requirements, user stories, roadmaps, prioritization frameworks, and sprint planning specialist. Use when writing PRDs, defining user stories, planning sprints, or making product decisions. Trigger phrases: PRD, user story, roadmap, sprint, backlog, prioritization, product requirements, acceptance criteria…
aiox-pm
AIOX Project Manager autônomo. Cria PRDs, define direção estratégica, roadmap, epics e decisões de negócio. Usa task files reais do AIOX.
aiox-po
AIOX Product Owner autônomo. Valida stories, gerencia backlog, garante coerência de epic context. Usa task files reais do AIOX.