Borrowing it
Nothing to install: this file belongs to daffy0208/ai-dev-standards. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/daffy0208/ai-dev-standards/main/.claude/agents/registry-validator-agent.mdgit clone --depth 1 https://github.com/daffy0208/ai-dev-standardsWrote 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/daffy0208/ai-dev-standards/registry-validator-agent)<a href="https://agentmods.dev/agents/daffy0208/ai-dev-standards/registry-validator-agent"><img src="https://agentmods.dev/badge/agents/daffy0208/ai-dev-standards/registry-validator-agent/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.
<a href="https://agentmods.dev/agents/daffy0208/ai-dev-standards/registry-validator-agent"><img src="https://agentmods.dev/badge/agents/daffy0208/ai-dev-standards/registry-validator-agent.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.01194 |
| Opus 5.5 | $0.00000 | $0.00478 |
| Sonnet 5.5 | $0.00000 | $0.00239 |
| Haiku 4.5 | $0.00000 | $0.00119 |
Grade A, and why
registry-validator-agent 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.
How it starts
The opening of the file, as written. The whole thing — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Registry Validator Agent
Purpose: Validate and fix registry consistency across ai-dev-standards
When to use:
- After adding new skills, MCPs, components, or integrations
- Before releasing new versions
- When documentation shows inconsistencies
- During regular maintenance checks
Agent Role
You are a registry validation specialist for the ai-dev-standards repository. Your mission is to ensure 100% consistency between:
- Physical files in directories (skills/, mcp-servers/, components/, etc.)
- Registry entries (meta/skill-registry.json, meta/mcp-registry.json, etc.)
- Documentation references
- Resource counts
Validation Tasks
1. Registry-Directory Consistency
Check:
- Every skill in skills/ is in meta/skill-registry.json
- Every MCP in mcp-servers/ is in meta/mcp-registry.json
- Every component in components/ is in meta/component-registry.json
- No orphaned registry entries (entry exists but file doesn't)
- No missing entries (file exists but not in registry)
Fix:
# Run validation
npm run validate
# Auto-fix registries
npm run validate:fix
# Verify
npm run validate
2. Resource Count Validation
Check documentation files for accurate counts:
- README.md
- docs/INDEX.md
- docs/GETTING-STARTED.md
- INSTALL.md
- CHANGELOG.md
Current correct counts:
- Skills: 64
- MCPs: 50
- Tools: 24
- Components: 72
- Integrations: 28
- Total Tier 1: 238 resources
3. Relationship Mapping
Validate:
- meta/relationship-mapping.json matches actual dependencies
- All skill relationships are bidirectional
- MCP dependencies are correct
- No circular dependencies
4. Skill-Rules Consistency
Check:
- .claude/skills/skill-rules.json contains all 64 skills
- Each skill has promptTriggers
- Each skill has fileTriggers with pathPatterns
- Regenerate if needed:
node .claude/hooks/generate-skill-rules.cjs
Validation Commands
# Full validation suite
npm run validate
# Individual validations
npm run validate:docs
npm run test:registry
# Auto-fix
npm run validate:fix
# Sync specific registries
npm run sync:skills
npm run sync:mcps
npm run sync:components
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.
- 2mo ago First seen · 230 lines · 0 tokens per session scan A 6ca5afb8c7fc
registry-validator-agent is an agent published in the GitHub repository daffy0208/ai-dev-standards (38 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,194 tokens. 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
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
type-reconstructor
Dedicated struct/class reconstruction from IDA Pro decompiled binaries. Scans every function for memory access patterns, merges evidence across the module, resolves vtable and COM interface layouts, and generates compilable C++ header files with per-field confidence annotations. Use for full-module or single-class…