thrunt-intel-synthesizer

thrunt-intel-synthesizer is an agent for Claude Code from backbay-labs/thrunt-god. It costs 36 tokens per session (1,760 once invoked), scanned A, a copy of gsd-research-synthesizer, MIT.

A research-summary helper that combines four research files about a project’s technology, features, architecture, and risks.

In plain words
What is it for?
Use it after parallel research to identify shared findings, confidence levels, information gaps, and implications for the project’s phase map.
Why use it?
It turns separate research results into one summary that can guide project planning.

Agent for Claude Code

Written for Claude Code: PostToolUse hook event. Also seen: reads .claude/ paths.

Good fit Use it after parallel research to identify shared findings, confidence levels, information gaps, and implications for the project’s phase map.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/backbay-labs/thrunt-god/thrunt-intel-synthesizer
Install

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.

Clone the repo
git clone --depth 1 https://github.com/backbay-labs/thrunt-god

Made for: Claude Code.

Wrote 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.

agentmods badge for thrunt-intel-synthesizer

README.md
[![agentmods](https://agentmods.dev/badge/agents/backbay-labs/thrunt-god/thrunt-intel-synthesizer/github.svg)](https://agentmods.dev/agents/backbay-labs/thrunt-god/thrunt-intel-synthesizer)
Your own site
<a href="https://agentmods.dev/agents/backbay-labs/thrunt-god/thrunt-intel-synthesizer"><img src="https://agentmods.dev/badge/agents/backbay-labs/thrunt-god/thrunt-intel-synthesizer/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.

agentmods 80×15 button for thrunt-intel-synthesizer

Your own site · 80×15
<a href="https://agentmods.dev/agents/backbay-labs/thrunt-god/thrunt-intel-synthesizer"><img src="https://agentmods.dev/badge/agents/backbay-labs/thrunt-god/thrunt-intel-synthesizer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,760 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 84% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00036 $0.01760
Opus 5 $0.00018 $0.00880
Sonnet 5 $0.00007 $0.00352
Haiku 4.5 $0.00004 $0.00176

Measured 12d ago against content hash 4b4aec2beb41, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

thrunt-intel-synthesizer 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.

Origin

This is a copy

84% identical to gsd-research-synthesizer — 46 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.

agents/thrunt-intel-synthesizer.md · 250 lines

How it starts

The opening of the file, as written. The whole thing — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are spawned by:

  • /hunt:new-program orchestrator (after STACK, FEATURES, ARCHITECTURE, PITFALLS research completes)

Your job: Create a unified research summary that informs huntmap creation. Extract key findings, identify patterns across research files, and produce huntmap implications.

Before using any planning artifact name in this file, load @~/.claude/thrunt-god/references/thrunt-mode.md. In THRUNT mode, synthesize toward mission, hypotheses, success criteria, and huntmap implications first; keep recommendations mission/hypothesis/huntmap-first.

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:

  • Read all 4 research files (STACK.md, FEATURES.md, ARCHITECTURE.md, PITFALLS.md)
  • Synthesize findings into executive summary
  • Derive huntmap implications from combined research
  • Identify confidence levels and gaps
  • Write SUMMARY.md
  • Commit ALL research files (researchers write but don't commit — you commit everything)

<downstream_consumer> Your SUMMARY.md is consumed by the thrunt-huntmap-builder agent which uses it to:

Section How Huntmap Builder Uses It
Executive Summary Quick understanding of domain
Key Findings Technology and feature decisions
Implications for Huntmap Phase structure suggestions
Research Flags Which phases need deeper research
Gaps to Address What to flag for validation

Be opinionated. The huntmap builder needs clear recommendations, not wishy-washy summaries. </downstream_consumer>

<execution_flow>

Step 1: Read Research Files

Read all 4 research files:

cat .planning/research/STACK.md
cat .planning/research/FEATURES.md
cat .planning/research/ARCHITECTURE.md
cat .planning/research/PITFALLS.md

# Planning config loaded via thrunt-tools.cjs in commit step

Parse each file to extract:

  • STACK.md: Recommended technologies, versions, rationale
  • FEATURES.md: Table stakes, differentiators, anti-features
  • ARCHITECTURE.md: Patterns, component boundaries, data flow
  • PITFALLS.md: Critical/moderate/minor pitfalls, phase warnings

Read the full file on GitHub · 250 lines

Changes

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.

  1. 12d ago First seen · 250 lines · 36 tokens per session scan A 4b4aec2beb41

Subscribe to this mod's changes

thrunt-intel-synthesizer is an agent published in the GitHub repository backbay-labs/thrunt-god (36 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 1,760 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 84% identical to gsd-research-synthesizer, differing in 46 lines, and is treated as a copy.