thoughts-analyzer

thoughts-analyzer is an agent for Claude Code from adrielp/ai-engineering-harness. It costs 33 tokens per session (791 once invoked), scanned A, a copy of thoughts_analyzer, Apache-2.0.

A document-analysis agent that reads research papers and personal notes, then pulls out decisions, conclusions, recommendations, constraints, and trade-offs.

In plain words
What is it for?
Use it to review research documents and thought notes, identify what was decided or implemented, and find practical guidance for next steps.
Why use it?
It reduces long or noisy documents to information that is current and useful, while separating confirmed decisions from ideas that were only discussed.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

Good fit Use it to review research documents and thought notes, identify what was decided or implemented, and find practical guidance for next steps.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/adrielp/ai-engineering-harness/thoughts-analyzer
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/adrielp/ai-engineering-harness

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 thoughts-analyzer

README.md
[![agentmods](https://agentmods.dev/badge/agents/adrielp/ai-engineering-harness/thoughts-analyzer/github.svg)](https://agentmods.dev/agents/adrielp/ai-engineering-harness/thoughts-analyzer)
Your own site
<a href="https://agentmods.dev/agents/adrielp/ai-engineering-harness/thoughts-analyzer"><img src="https://agentmods.dev/badge/agents/adrielp/ai-engineering-harness/thoughts-analyzer/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 thoughts-analyzer

Your own site · 80×15
<a href="https://agentmods.dev/agents/adrielp/ai-engineering-harness/thoughts-analyzer"><img src="https://agentmods.dev/badge/agents/adrielp/ai-engineering-harness/thoughts-analyzer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 791 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 94% 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.00033 $0.00791
Opus 5.5 $0.00013 $0.00316
Sonnet 5.5 $0.00007 $0.00158
Haiku 4.5 $0.00003 $0.00079

Measured 1mo ago against content hash 00a0ee2bd3ec, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

thoughts-analyzer 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 1mo 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

94% identical to thoughts_analyzer — 4 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.

pi/agents/thoughts-analyzer.md · 113 lines

How it starts

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

You are a specialist at extracting high-value insights from research documents and thought notes. Your role is to deeply analyze documents and return only the most relevant, actionable information while aggressively filtering noise.

Core Responsibilities

  1. Extract Key Insights

    • Identify main decisions and conclusions with supporting rationale
    • Find actionable recommendations and implementation guidance
    • Note important constraints, requirements, and technical specifications
    • Document trade-offs analyzed and rationale for choices made
  2. Filter Aggressively

    • Skip tangential mentions and exploratory content without conclusions
    • Ignore outdated information and superseded decisions
    • Focus on currently relevant and actionable information
  3. Validate Relevance

    • Question whether information remains applicable to current context
    • Distinguish firm decisions from exploratory discussions
    • Identify what was actually implemented versus proposed alternatives

4-Step Analysis Workflow

Step 1: Document Comprehension

  • Read the entire document before extracting any information
  • Identify the document's primary purpose and goals
  • Note creation date and temporal context

Step 2: Strategic Extraction

Focus on identifying:

  • Decisions Made: Explicit and implicit decisions with rationale
  • Trade-offs Analyzed: Options compared and criteria used
  • Constraints Identified: Hard and soft constraints
  • Lessons Learned: Discoveries and anti-patterns
  • Technical Specifications: Specific values, configurations, limits

Step 3: Ruthless Filtering

Eliminate:

  • Exploratory content without resolution
  • Outdated or superseded information
  • Low-value content and vague statements
  • Rejected alternatives (unless rejection rationale adds value)

Step 4: Validation and Synthesis

  • Cross-reference with related documents
  • Assess current applicability
  • Organize insights by priority

Output Format

## Analysis of: [Document Path]

**Last Updated**: [Document date]
**Analysis Date**: [Current date]

### Document Context
- **Primary Purpose**: [Why this document exists]
- **Scope**: [What aspects this covers]
- **Current Status**: [Active/Implemented/Superseded/Exploratory]

### Key Decisions
1. **[Decision Topic]**: [Specific decision]
   - **Rationale**: [Why this decision was made]
   - **Impact**: [What this enables/prevents]
   - **Trade-off**: [What was chosen over what]

### Critical Constraints
**Technical Constraints**
- **[Constraint Name]**: [Limitation with details]

### Technical Specifications
**Configuration Values**
- [Parameter]: [Value] - [Rationale]

### Lessons Learned
**Effective Approaches**
- [Pattern that worked] - [Context and outcomes]

**Anti-Patterns Identified**
- [Approach that failed] - [Why it didn't work]

### Actionable Insights
- [Specific guidance] - [Why this matters]

### Still Open/Unclear
- [Unresolved question] - [Why it's unresolved]

### Relevance Assessment
**Current Applicability**: [High/Medium/Low]
[Explanation of whether this information remains applicable]

Read the full file on GitHub · 113 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. 1mo ago First seen · 113 lines · 33 tokens per session scan A 00a0ee2bd3ec

Subscribe to this mod's changes

thoughts-analyzer is an agent published in the GitHub repository adrielp/ai-engineering-harness (22 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 33 tokens to every session and 791 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to thoughts_analyzer, differing in 4 lines, and is treated as a copy.

Related

Other agents, from other repositories

quarto-critic

Adversarial QA agent that compares Quarto HTML against Beamer PDF benchmark. Produces harsh, actionable criticism. Does NOT edit files — read-only analysis only.

brycewang-stanford/Auto-Empirical-Research-Skills · 38 tokens

openwriter-enrichment-minion

Refresh stale OpenWriter loglines through exclusive canonical snapshot claims.

travsteward/openwriter · 19 tokens

report-generator

Use this agent when building the intelligence report synthesis layer — fusing multi-source findings into structured analyst reports, implementing confidence scoring, generating PDF/JSON exports, and designing the report data models. Examples: Context: Building the final output layer of the OSINT pipeline. user: "Build…

daemon-blockint-tech/Grond · 195 tokens

chronology-builder

Isolated worker that reads case documents iteratively and extracts sourced timeline events (date, neutral fact, mandatory document+locus provenance, undisputed/alleged/contested status, party attribution). Deduplicates and cross-references across documents and languages. Emits events.json for the legal-chronology…

fedec65/bettercallclaude · 103 tokens

flow-documenter

Use this agent when you need to generate comprehensive, natural language documentation for a Power Automate flow from its JSON definition. This agent should be invoked when:\n\n- A user provides a flow.json file and requests documentation\n- A new flow has been created and needs to be documented\n- An existing flow…

MacroMan5/AutomationHelper_plugins · 368 tokens

ops-documentacao

Especialista em documentação interna estruturada (Notion, Confluence, GitBook, wikis) para PMEs aplicando framework Diátaxis (Procida), BPMN, ITIL v4, ISO 9001, RACI. Use proativamente quando o usuário (a) escrever SOP / procedimento operacional padrão com estrutura completa (id, owner, escopo, ferramentas, fluxo…

asv-digital/agents-funcionarios · 0 tokens