ecosystem-integrity-scanner

name	ecosystem-integrity-scanner
description	Deeply analyzes Agent Studio framework structural health: catching phantom require() references, wrong module depth paths, missing skill/agent dependencies, bloated configurations, archived references in active code, stale catalog counts, and empty tool/skill directories.
version	1.1.0
model	sonnet
category	validation
invoked_by	both
user_invocable	true
tools	["Read","Bash","Glob","Grep"]
agents	["qa","developer","architect"]
best_practices	["Always run validate-ecosystem-integrity.cjs from project root","Route PHANTOM_REQUIRE errors to developer for immediate fix","Save audit reports to .claude/context/reports/qa/","Treat 0 errors as the only acceptable completion state"]
error_handling	strict
streaming	supported
verified	true
lastVerifiedAt	"2026-02-22T00:00:00.000Z"
source	builtin
trust_score	100
provenance_sha	b5a1fc74c0c14d01

Ecosystem Integrity Scanner

Overview

Automated structural integrity scanner for the entire Agent Studio framework. Catches issues that silently break agent workflows: wrong require() paths that crash at runtime, phantom skills referenced in agent frontmatter that don't exist on disk, stale agent registry counts, archived references still active in production code, UTF-16 encoding that breaks parsers, and bloated agent configs.

Core principle: Framework structural issues are pre-production bugs. A phantom skill reference means an agent will fail silently. A broken require() means a hook crashes at the wrong moment. The scanner enforces zero-tolerance for these.

When to Invoke

Skill({ skill: 'ecosystem-integrity-scanner' });

Invoke proactively after:

• Bulk framework changes (batch skill/agent/hook creation or archiving)
• Refactoring module paths or directory structure
• Running a major audit or cleanup pass
• Suspecting phantom references or broken require() chains
• Before finalizing any CI sanity gate

Mandatory Skills

Invoke before starting this skill:

Skill	Purpose	When
task-management-protocol	Track scan progress	Always
ripgrep	Fast targeted code search	When investigating
code-semantic-search	Concept discovery	When pattern hunting
context-compressor	Compress large audit results	When output is large
verification-before-completion	Gate completion on zero errors	Before marking done
memory-search	Check prior audit patterns	At start

Iron Laws

1. Always run from project root. validate-ecosystem-integrity.cjs resolves all paths relative to process.cwd(). Running from a subdirectory corrupts all path resolution. Never invoke from a non-root directory.