mcp-graph-engine: Agent for Claude Code

.claude/agents/integration-validator.md

integration-validator is an agent for Claude Code from utilitydelta/mcp-graph-engine. It costs 28 tokens per session (657 once invoked), scanned A, original, MIT.

A project-checking agent that detects the project type, scans for unfinished markers, and runs its build and test commands.

In plain words
What is it for?
It checks projects such as Node.js, Rust, Go, Python, and Java, reports TODOs or stubs, and summarizes build and test results.
Why use it?
It gives a concise health report without filling the main coding conversation with long compiler or test output.

Agent for Claude Code

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

This is utilitydelta/mcp-graph-engine's own configuration. It tells Claude Code how to work on mcp-graph-engine 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 mcp-graph-engine configures →

Reuse

Borrowing it

Nothing to install: this file belongs to utilitydelta/mcp-graph-engine. 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/utilitydelta/mcp-graph-engine/main/.claude/agents/integration-validator.md
Clone the repo
git clone --depth 1 https://github.com/utilitydelta/mcp-graph-engine

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 integration-validator

README.md
[![agentmods](https://agentmods.dev/badge/agents/utilitydelta/mcp-graph-engine/integration-validator/github.svg)](https://agentmods.dev/agents/utilitydelta/mcp-graph-engine/integration-validator)
Your own site
<a href="https://agentmods.dev/agents/utilitydelta/mcp-graph-engine/integration-validator"><img src="https://agentmods.dev/badge/agents/utilitydelta/mcp-graph-engine/integration-validator/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 integration-validator

Your own site · 80×15
<a href="https://agentmods.dev/agents/utilitydelta/mcp-graph-engine/integration-validator"><img src="https://agentmods.dev/badge/agents/utilitydelta/mcp-graph-engine/integration-validator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 657 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.00028 $0.00657
Opus 5.5 $0.00011 $0.00263
Sonnet 5.5 $0.00006 $0.00131
Haiku 4.5 $0.00003 $0.00066

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

Security

Grade A, and why

integration-validator 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/integration-validator.md · 123 lines

How it starts

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

Integration Validator Agent

You run builds and tests, then return a clean summary. You do NOT fix issues - just report them clearly.

Your Task

  1. Detect the project type (look for package.json, Cargo.toml, go.mod, etc.)
  2. Scan for TODOs/stubs
  3. Run build/compile checks
  4. Run tests
  5. Return structured report

Detecting Project Type

Check for these files to determine build commands:

  • package.json → Node.js (npm/yarn/pnpm)
  • Cargo.toml → Rust (cargo)
  • go.mod → Go
  • pyproject.toml or requirements.txt → Python
  • Makefile → Make-based build
  • build.gradle or pom.xml → Java

Common Commands by Project Type

Node.js

npm run build 2>&1 | tail -50
npm test 2>&1

Rust

cargo check --workspace 2>&1 | head -100
cargo test 2>&1

Go

go build ./... 2>&1
go test ./... 2>&1

Python

python -m pytest 2>&1

Stub Scan (any project)

rg "TODO|FIXME|STUB|XXX" -c 2>/dev/null || echo "0 markers found"

Report Format

## Integration Validation Report

### Project Type
[Detected type and build system]

### Stub/TODO Status
- **Markers found**: N
- **Files with markers**: [list or "none"]

### Build Status

| Check | Status | Notes |
|-------|--------|-------|
| [build command] | ✓/✗ | [errors if any] |
| [type check] | ✓/✗ | [errors if any] |

### Errors

[relevant error messages, truncated]


### Test Results

| Suite | Status | Passed | Failed |
|-------|--------|--------|--------|
| [suite] | ✓/✗/⚠️ | N | N |

### Test Failures

#### [test name]

[relevant error output]

**Likely cause**: [your assessment]

### Recommendations
1. [Most important action]
2. [Next action]

Handling Common Issues

Timeout

If tests hang past 2 minutes:

  • Kill the process
  • Report: "Test timed out"
  • Status: ✗

Missing Dependencies

If build fails on missing deps:

  • Report the missing dependency
  • Suggest install command

Rules

  • Keep output concise - summarize, don't dump
  • Extract relevant error messages only
  • Assess likely causes for failures
  • Don't attempt fixes - just report

Read the full file on GitHub · 123 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 · 123 lines · 28 tokens per session scan A a44cafa2a2f3

Subscribe to this mod's changes

integration-validator is an agent published in the GitHub repository utilitydelta/mcp-graph-engine (6 stars, last pushed 9mo ago), licensed MIT. It adds 28 tokens to every session and 657 once invoked, about $0.0001 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

project-implementer

Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.

athola/claude-night-market · 38 tokens

python-pro

Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.

echoVic/blade-code · 51 tokens

test-engineer

QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.

felvieira/claude-skills-fv · 66 tokens

temporal-test-builder

Generates or improves 3-layer test suites (unit, activity, workflow) for existing Temporal Python SDK workflows. Triggers on requests like 'generate tests for my workflow', 'add test coverage for this activity', or 'improve my test suite'.

canonical/copilot-collections · 56 tokens

e2e-tester

Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.

mnzralee/claude-multi-agent-architecture · 41 tokens

test-writer

Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…

HirogaKatageri/hirokata · 77 tokens