ip-intelligence: Agent for Claude Code

.claude/agents/repair-engineer.md

repair-engineer is an agent for Claude Code from ard1102/ip-intelligence. It costs 135 tokens per session (2,450 once invoked), scanned A, original, MIT.

An agent for implementing automatic repair and health monitoring for data feeds in the IP Intel Platform. It tracks feed failures and moves feeds through states such as healthy, degraded, quarantined, restored, and escalated.

In plain words
What is it for?
It is for building the platform's repair agent and scheduler, retrying recoverable failures, quarantining schema changes, rolling back bad data, and sending unresolved failures to an alert webhook.
Why use it?
It provides defined responses when a feed stops responding, changes its data structure, returns too little data, or repeatedly returns unchanged content.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is ard1102/ip-intelligence's own configuration. It tells Claude Code how to work on ip-intelligence itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ip-intelligence configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ard1102/ip-intelligence. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ard1102/ip-intelligence/master/.claude/agents/repair-engineer.md
Clone the repo
git clone --depth 1 https://github.com/ard1102/ip-intelligence

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 repair-engineer

README.md
[![agentmods](https://agentmods.dev/badge/agents/ard1102/ip-intelligence/repair-engineer/github.svg)](https://agentmods.dev/agents/ard1102/ip-intelligence/repair-engineer)
Your own site
<a href="https://agentmods.dev/agents/ard1102/ip-intelligence/repair-engineer"><img src="https://agentmods.dev/badge/agents/ard1102/ip-intelligence/repair-engineer/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 repair-engineer

Your own site · 80×15
<a href="https://agentmods.dev/agents/ard1102/ip-intelligence/repair-engineer"><img src="https://agentmods.dev/badge/agents/ard1102/ip-intelligence/repair-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 135 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,450 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.00135 $0.02450
Opus 5.5 $0.00054 $0.00980
Sonnet 5.5 $0.00027 $0.00490
Haiku 4.5 $0.00014 $0.00245

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

Security

Grade A, and why

repair-engineer 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 2mo 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.

.claude/agents/repair-engineer.md · 263 lines

How it starts

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

You are a Repair Engineer specialist for the IP Intel Platform. Your job is to implement the SelfRepairAgent class and APScheduler configuration.

Failure Taxonomy (memorize this exactly)

  1. liveness — HTTP probe fails (timeout, DNS failure, 4xx/5xx). 3 retries with 300s backoff.
  2. schema_drift — Column set mismatch vs health_contract.required_columns. IMMEDIATE quarantine, no retry.
  3. data_quality — Record count below min_records. 3 retries, then rollback to last good snapshot.
  4. content_drift — SHA-256 hash of raw response bytes identical across 5 consecutive pulls AND cadence < 60 min. Informational only — log and continue, NEVER quarantine.

State Machine

HEALTHY → (failure) → DEGRADED → (3 retries OR schema_drift) → QUARANTINED QUARANTINED → (repair succeeds) → RESTORED QUARANTINED → (repair fails) → ESCALATED → POST to ALERT_WEBHOOK_URL

FeedStatus Enum (use exactly these values)

class FeedStatus(Enum):
    HEALTHY = "healthy"
    DEGRADED = "degraded"
    QUARANTINED = "quarantined"
    RESTORED = "restored"
    ESCALATED = "escalated"

FeedHealthRecord Dataclass (use exactly these fields — copy verbatim)

@dataclass
class FeedHealthRecord:
    feed_id: str
    status: FeedStatus
    last_healthy: datetime
    last_checked: datetime
    failure_type: str | None = None
    failure_detail: str | None = None
    retry_count: int = 0
    content_hash: str | None = None
    record_count: int = 0
    rolling_count_avg: float = 0.0
    schema_hash: str | None = None
    repair_attempts: int = 0
    repair_log: list[str] = field(default_factory=list)

SelfRepairAgent.init signature

def __init__(self, store: IntelStore, feeds: list[FeedConfig], alert_webhook: str):
    self.store = store
    self.feeds = {f.id: f for f in feeds}
    self.alert_webhook = alert_webhook
    self.health_records: dict[str, FeedHealthRecord] = {}
    self.content_hash_history: dict[str, list[str]] = {}

Read the full file on GitHub · 263 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. 2mo ago First seen · 263 lines · 135 tokens per session scan A 13b8f0e4be75

Subscribe to this mod's changes

repair-engineer is an agent published in the GitHub repository ard1102/ip-intelligence (0 stars, last pushed 3mo ago), licensed MIT. It adds 135 tokens to every session and 2,450 once invoked, about $0.0005 per session on Opus 5.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.

Related

Other agents, from other repositories

dgx-spark-ops-engineer

NVIDIA DGX Spark environment doctor for GB10/aarch64/CUDA-13 systems. Diagnoses and fixes ML stack setup, unified-memory, and thermal issues. Use PROACTIVELY when preparing or debugging any training or inference workload on DGX Spark hardware.

wshobson/agents · 63 tokens

workflow-prompt-writer

Use this agent when writing, reviewing, or debugging LLM prompt files (.prompt). Specializes in Liquid.js template syntax, YAML frontmatter configuration, and Output SDK prompt conventions.

growthxai/output · 42 tokens

pytorch-build-resolver

PyTorch runtime, CUDA, and training error resolution specialist. Fixes tensor shape mismatches, device errors, gradient issues, DataLoader problems, and mixed precision failures with minimal changes. Use when PyTorch training or inference crashes.

loulanyue/awesome-claude-notes · 52 tokens

alchemist

Code/data transmutation via four-stage alchemical process (nigredo/albedo/citrinitas/rubedo) with meditate/heal checkpoints.

pjt222/agent-almanac · 32 tokens

integration-checker

Validates that analysis components are properly connected by tracing data flows, verifying file references resolve, and detecting orphaned components. Invoked by orchestrator at Stages 9, 11, and 12 to confirm end-to-end pipeline wiring.

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

pixeltable-debugger

Diagnoses failing or stale Pixeltable pipelines. Errored computed columns, no-op recomputes, retrieval problems, rate limits, deprecated-API misuse. Use when Pixeltable code errors, returns empty/stale results, or behaves unexpectedly.

pixeltable/pixeltable-skill · 56 tokens