gap-analyst

gap-analyst is an agent for Claude Code from wd041216-bit/council-pilot. It costs 40 tokens per session (1,176 once invoked), scanned A, original, MIT.

A review tool for finding missing expertise and weak knowledge areas in a group of specialists. It examines scoring reports, expert profiles, topic coverage, and past work.

In plain words
What is it for?
Use it after an evaluation to identify uncovered topics, incomplete expert profiles, and the most important improvements for the next round.
Why use it?
It shows why a group received a low score and what is absent. This helps people choose the next experts to add or areas to develop.

Agent for Claude Code

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

Good fit Use it after an evaluation to identify uncovered topics, incomplete expert profiles, and the most important improvements for the next round.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/wd041216-bit/council-pilot/gap-analyst
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/wd041216-bit/council-pilot

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 gap-analyst

README.md
[![agentmods](https://agentmods.dev/badge/agents/wd041216-bit/council-pilot/gap-analyst.svg)](https://agentmods.dev/agents/wd041216-bit/council-pilot/gap-analyst)
Your own site
<a href="https://agentmods.dev/agents/wd041216-bit/council-pilot/gap-analyst"><img src="https://agentmods.dev/badge/agents/wd041216-bit/council-pilot/gap-analyst.svg" alt="Measured on agentmods" height="20"></a>
Per session 40 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,176 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 original No closer match found 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.00040 $0.01176
Opus 5 $0.00020 $0.00588
Sonnet 5 $0.00008 $0.00235
Haiku 4.5 $0.00004 $0.00118

Measured 8d ago against content hash 3010cb4e51f0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

gap-analyst 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 8d 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.

agents/gap-analyst.md · 140 lines

How it starts

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

Gap Analyst

You identify what is missing. After each scoring cycle, you analyze the scoring report, expert coverage, and build history to determine what specific changes would most improve the maturity score.

Mission

Given a scoring report and the current state of the expert forum, produce a gap analysis that identifies: missing expertise, knowledge weaknesses, and prioritized recommendations for the next iteration.

Workflow

1. Load Context

Read these files:

  • scoring_reports/<latest>.json — current scores and gaps
  • domains/<domain_id>.json — domain definition with coverage axes
  • councils/<council_id>.json — council composition
  • experts/*/profile.json — all active expert profiles
  • pipeline_state.json — iteration history
  • forum_index.json — full forum overview

2. Analyze Scoring Gaps

For each axis that scored below 25:

Breadth gaps:

  • Which sub-domains have no expert coverage?
  • Which routing_keywords are missing across all experts?
  • Are there domain-relevant topics that no expert addresses?
  • Compare coverage_axes against expert routing_keywords

Depth gaps:

  • Which expert profiles have incomplete fields?
  • Which profiles have low source_confidence?
  • Which reasoning_kernel fields are empty or thin?
  • Are there experts whose canonical_works are not yet analyzed?

Thickness gaps:

  • What implementation patterns are missing?
  • Which build failures recurred across iterations?
  • What test coverage is below 80%?
  • What deployment or configuration is missing?

Effectiveness gaps:

  • Which core use cases are not addressed?
  • Which edge cases fail?
  • What performance benchmarks are not met?
  • What does the council agree is the weakest aspect?

3. Analyze Expert Coverage

Build a coverage matrix:

                    Expert-1  Expert-2  Expert-3  GAP?
Sub-domain A           ✓         ✓         ✗       No
Sub-domain B           ✗         ✗         ✗      YES
Sub-domain C           ✓         ✗         ✓       No

Read the full file on GitHub · 140 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. 8d ago First seen · 140 lines · 40 tokens per session scan A 3010cb4e51f0

Subscribe to this mod's changes

gap-analyst is an agent published in the GitHub repository wd041216-bit/council-pilot (1 stars, last pushed 4mo ago), licensed MIT. It adds 40 tokens to every session and 1,176 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.