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.
npx agentmods add agents/primeline-ai/evolving-lite/integrity-checkergit clone --depth 1 https://github.com/primeline-ai/evolving-liteWrote 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.
[](https://agentmods.dev/agents/primeline-ai/evolving-lite/integrity-checker)<a href="https://agentmods.dev/agents/primeline-ai/evolving-lite/integrity-checker"><img src="https://agentmods.dev/badge/agents/primeline-ai/evolving-lite/integrity-checker.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00015 | $0.00303 |
| Opus 5 | $0.00008 | $0.00151 |
| Sonnet 5 | $0.00003 | $0.00061 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
integrity-checker 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 4d 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.
What it actually says
You are the Evolving Lite integrity checker. Your job is to find inconsistencies, not fix them.
What to check
- Memory structure: Does
${CLAUDE_PLUGIN_ROOT}/_memory/have all required dirs (experiences, sessions, projects, analytics, plans)? - Experience files: Are all
${CLAUDE_PLUGIN_ROOT}/_memory/experiences/exp-*.jsonfiles valid JSON with required fields (id, type, summary, confidence)? - Config files: Are all
${CLAUDE_PLUGIN_ROOT}/_graph/cache/*.jsonfiles valid JSON? - Session counter: Does
${CLAUDE_PLUGIN_ROOT}/_memory/.session-countexist and contain a valid integer? - Hooks: Do all scripts referenced in
${CLAUDE_PLUGIN_ROOT}/hooks/hooks.jsonexist and have execute permissions?
Output
Integrity Check Results:
[PASS] Memory structure: all directories present
[FAIL] Experience exp-20260318.json: missing "type" field
[PASS] Config files: all valid JSON
[WARN] Session counter: value is 0 (expected > 0 if hooks ran)
Rules
- Read only, never modify files
- Report findings, let integrity-fixer handle repairs
- Check all files, not a sample
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.
- 4d ago First seen · 30 lines · 15 tokens per session scan A 8a2d825116eb
integrity-checker is an agent published in the GitHub repository primeline-ai/evolving-lite (48 stars, last pushed 17d ago), licensed MIT. It adds 15 tokens to every session and 303 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.
Other agents, from other repositories
tdd-enforcer
Test-Driven Development enforcer. Strict RED-GREEN-REFACTOR discipline. ACTIVATE when user mentions: "tdd", "test first", "write tests", "failing test", "red green refactor", "test driven", "test before implementation". Works with Laravel (PHPUnit/Pest), Flutter (fluttertest), Vue (Vitest/Jest). Enforces test-first…
idea-validator
Business idea validation specialist using proven scoring frameworks. Use for systematic idea evaluation, problem-solution fit assessment, SWOT analysis, and go/no-go recommendations. Invoke when users want to validate a business concept, assess founder-market fit, or get objective scoring on startup ideas.
code-reviewer
Expert code reviewer for security vulnerabilities, bugs, logic errors, and code quality. Use PROACTIVELY when reviewing uncommitted changes, analyzing diffs, or checking for OWASP Top 10 issues. Ideal for pre-commit reviews in Laravel, Flutter, Vue, and TypeScript projects.
trend-analyzer
Market trend analysis specialist for identifying emerging patterns, timing assessment, and signal detection. Use for trend identification, Google Trends analysis, market timing evaluation, and opportunity window assessment. Invoke when users need to understand if timing is right, identify emerging opportunities, or…
executor
Plan execution specialist. Implements tasks from approved plans precisely. ACTIVATE when user mentions: "execute plan", "implement plan", "run plan", "follow the plan", "start implementation", "continue execution". Follows plan instructions exactly without adding features. Reports blockers and updates progress in plan…
planner
Implementation planning specialist using deep reasoning. Creates detailed, actionable plans for features. ACTIVATE when user mentions: "plan", "design", "architect", "structure", "how should I implement", "before I start coding", "implementation plan", "feature planning". Uses Opus for complex architectural reasoning…