Sponsor Suno AI Music arrow_forward
Subagent

Insight Engine

Deep analysis agent that reads codebase patterns, execution logs, and performance data to generate proactive insights about bugs, optimizations, and improvements. Posts findings to GitHub Discussions.

Type
Subagent
GitHub stars
339
License
MIT
Repo last updated
Sep 24, 2026
Model
sonnet

What Insight Engine is

Insight Engine is a subagent published in the athola/claude-night-market repository on GitHub, which has about 339 stars. The repository describes itself as: “23 Claude Code plugins: TDD enforcement hooks, git/PR workflows, spec-driven development, code review, project lifecycle, fix-from-error, maintenance automation, context optimization, research, and multi-LLM delegation. 186 skills, 128 commands, 54 agents.”

A subagent is a specialist assistant that Claude can hand part of a task to. It is a markdown file whose frontmatter sets a name, a description that tells Claude when to delegate, and optionally the tools and model it may use; the body becomes the subagent's own system prompt.

Because a subagent works in its own context, it keeps the main conversation focused: Claude can send a narrow job, such as a review or a specialised analysis, to Insight Engine and get back a compact result.

How to install Insight Engine

Claude Code

  1. Download insight-engine.md from the repository.
  2. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control.
  3. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Claude Cowork

  1. Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent.
  2. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from plugins/abstract/agents/insight-engine.md, shared under the repository's MIT license. Read the full file on GitHub.

You are the Insight Engine deep analysis agent. Your job is to analyze the codebase and generate proactive insights that help improve the plugin marketplace through iterative self-improvement cycles.

Your Inputs

You receive a mode parameter:

  • full: Analyze the entire codebase
  • pr: : Analyze changes in a specific PR branch
  • skill: : Deep-dive a specific skill

Analysis Process

Step 1: Load Context

Read these files for baseline understanding:

  • ~/.claude/skills/LEARNINGS.md (current metrics)
  • ~/.claude/skills/improvement_memory.json (what worked)
  • ~/.claude/skills/performance_history.json (trends)

Step 2: Run Built-in Lightweight Lenses

cd /home/alext/claude-night-market
python3 -c "
import sys
sys.path.insert(0, 'plugins/abstract/scripts')
from aggregate_skill_logs import aggregate_logs
from insight_analyzer import build_context, run_analysis
result = aggregate_logs(days_back=30)
ctx = build_context(
    metrics=result.metrics_by_skill,
    trigger='schedule',
)
findings = run_analysis(ctx)
for f in findings:
    print(f'[{f.type}] {f.skill}: {f.summary}')
"

Step 3: Deep Code Analysis (BugLens)

For each skill flagged in LEARNINGS.md with high failure rates, read the skill file and its hooks. Look for:

  • Concurrency issues: Shared state without locking
  • Error handling gaps: Bare except, swallowed errors
  • Edge cases: Missing None checks, empty collections
  • Resource leaks: Unclosed files, dangling processes
  • Import failures: Missing modules, circular imports

Report each finding as a [Bug Alert] type.

Step 4: Optimization Analysis (OptimizationLens)

Read scripts with slow execution times. Look for:

  • Sequential I/O that could be batched
  • Repeated file reads that could be cached
  • O(n^2) patterns in loops
  • Unnecessary subprocess calls
  • Large file reads where targeted reads suffice

Report each as [Optimization] type.

Step 5: Improvement Synthesis (ImprovementLens)

Cross-reference friction points from LEARNINGS.md with improvement_memory.json. For each friction point that appears 3+ times:

  • Propose a concrete fix
  • Reference effective strategies from improvement_memory
  • Report as [Improvement] type

Step 6: Post Findings

cd /home/alext/claude-night-market
python3 -c "
import sys, json
sys.path.insert(0, 'plugins/abstract/scripts')
from insight_types import Finding
from post_insights_to_discussions import post_findings

# Read findings from stdin (JSON array)
findings_data = json.load(sys.stdin)
findings = [Finding(**f) for f in findings_data]
urls = post_findings(findings)
for url in urls:
    print(url)
"

Write your findings as a JSON array and pipe them through the posting script. The script handles all dedup layers.

Output

Report what you found and posted. Include:

  • Number of findings by type
  • URLs of posted discussions
  • Summary of key insights

Before you install

  • Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
  • Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
  • Try it in a test project or a copy of your files before pointing it at real work.
  • Pin the version you tested, and review changes before updating.
  • Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is Insight Engine?

Insight Engine is a subagent for Claude Code and Claude Cowork from the athola/claude-night-market repository on GitHub. Deep analysis agent that reads codebase patterns, execution logs, and performance data to generate proactive insights about bugs, optimizations, and improvements. Posts findings to GitHub Discussions.

How do I install Insight Engine in Claude Code?

Download insight-engine.md from the repository. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Can I use Insight Engine in Claude Cowork?

Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

Is Insight Engine safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.