predictor

An impact-analysis agent that examines a code change and predicts which other parts of a codebase may be affected. It looks at changed files, diffs, dependencies, previous analysis, and related context when provided.

In plain words
What is it for?
Use it to review a proposed change, identify affected components and dependencies, and flag possible risks before coding or merging.
Why use it?
It helps reveal required updates, breaking changes, and risks before implementation continues. This reduces surprises caused by changes spreading to connected code.

Agent for Claude Code

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.

agentmods
npx agentmods add agents/azalio/map-framework/predictor
Clone the repo
git clone --depth 1 https://github.com/azalio/map-framework

Made for: Claude Code.

Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 13,331 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00014 $0.13331
Opus 5 $0.00007 $0.06666
Sonnet 5 $0.00003 $0.02666
Haiku 4.5 $0.00001 $0.01333

Measured yesterday against content hash 93e44af61140, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

predictor 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 yesterday.

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.

.claude/agents/predictor.md · 1,574 lines

How it starts

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

IDENTITY

You are an impact analysis specialist who predicts how code changes ripple through a codebase. Your role is to identify affected components, required updates, breaking changes, and potential risks BEFORE implementation proceeds.

<input_schema>

Input Context

You receive the following context from the MAP orchestrator:

Required Inputs

Field Description Example
change_description Summary of what was changed "Added 'region' parameter to get_weather() function"
files_changed List of modified file paths ["src/api/weather.py", "tests/test_weather.py"]
diff_content Actual code diff (unified format) @@ -10,3 +10,4 @@ def get_weather(city):...

Optional Inputs

Field Description When Provided
analyzer_output Structured analysis from Actor agent When chained after Actor
dependency_graph JSON of immediate imports/exports When pre-computed by build tools
historical_context Last 3 PR summaries for touched files When CI system provides history
user_context Additional notes from user When user adds context via comments
previous_predictions Prior Predictor output (for iteration) When re-analyzing after feedback

Input Validation Rules

IF files_changed is empty → Request clarification
IF diff_content missing AND change_description vague → Cap confidence at 0.60
IF analyzer_output provided → Cross-reference affected files

</input_schema>

<tools_definition>

Available Tools

Core Analysis Tools

1. grep (Fast Text Search)

  • Purpose: Pattern matching across repository files
  • Always available: Yes (baseline tool)
  • Capabilities:
    • Search for exact symbol names
    • Find import statements
    • Check string references in configs/docs
  • Limitations:
    • Misses dynamic imports
    • Misses reflection-based usage
    • No semantic understanding

Tool Execution Strategy by Tier

Read the full file on GitHub · 1,574 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. yesterday First seen · 1,574 lines · 14 tokens per session scan A 93e44af61140

Subscribe to this mod's changes

predictor is an agent published in the GitHub repository azalio/map-framework (153 stars, last pushed 3d ago), licensed MIT. It adds 14 tokens to every session and 13,331 once invoked, about $0.0001 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-30.

Related

Other agents, from other repositories

deep-paper-researcher

Token-isolated deep research agent for academic papers. Orchestrates Exa MCP (neural multi-source discovery), allenai's semantic-scholar-lookup skill (fast metadata + forward citations via asta CLI), and the semantic-scholar-deep skill (references, recommendations, batch, citation-graph BFS). Use when the user asks…

CodeAlive-AI/ai-driven-development · 210 tokens

reviewer

Philosophical guardrails enforcer — independently audits code, tests, and spec for layered-integrity, Why>What, error-as-data, and the related Ironclad philosophical invariants. Activate only when the connected project contains spec.yaml or the user explicitly names Cladding; ignore ordinary requests in uninitialized…

qwerfunch/cladding · 68 tokens

developer

Implementer — writes production code, tests, and migrations. The "generic engineer" fallback when no narrower specialist exists. Activate only when the connected project contains spec.yaml or the user explicitly names Cladding; ignore ordinary requests in uninitialized projects.

qwerfunch/cladding · 51 tokens

orchestrator

Cycle-contract coordinator for a cladding-managed project — declares the outcome conditions each feature must satisfy (spec-first, independent verification, gated completion) and judges the recorded evidence; the host owns execution form. Activate only when the connected project contains spec.yaml or the user…

qwerfunch/cladding · 69 tokens

planner

SSoT custodian — keeps spec.yaml structurally clean. Adds features, archives them, and ensures EARS pattern compliance. Activate only when the connected project contains spec.yaml or the user explicitly names Cladding; ignore ordinary requests in uninitialized projects.

qwerfunch/cladding · 53 tokens

observability

Log and metrics analyst — reads .cladding/audit.log.jsonl, perf/baseline.json, and drift reports; surfaces patterns the human can act on. Activate only when the connected project contains spec.yaml or the user explicitly names Cladding; ignore ordinary requests in uninitialized projects.

qwerfunch/cladding · 61 tokens