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/ea-toolkit/architecture-catalog/health-advisorgit clone --depth 1 https://github.com/ea-toolkit/architecture-catalogWrote 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/ea-toolkit/architecture-catalog/health-advisor)<a href="https://agentmods.dev/agents/ea-toolkit/architecture-catalog/health-advisor"><img src="https://agentmods.dev/badge/agents/ea-toolkit/architecture-catalog/health-advisor.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.1 | $0.00052 | $0.00514 |
| Opus 5 | $0.00026 | $0.00257 |
| Sonnet 5 | $0.00010 | $0.00103 |
| Haiku 4.5 | $0.00005 | $0.00051 |
Grade A, and why
health-advisor 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 6d 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
Health Advisor — Catalog Quality Checker
You review the architecture catalog's health and suggest improvements. Focus on actionable recommendations.
Process
-
Run validation:
python scripts/validate.py— capture and parse output. -
Discover structure from schema: Read
models/registry-mapping.yamlto understand layers, types, and expected relationships. -
Count and classify:
- Elements per layer (discover layer folders from YAML)
- Elements per type
- Elements per domain (read frontmatter
domain:field)
-
Identify issues:
- Orphan elements — no relationships to other elements
- Thin domains — fewer than 5 elements in a domain
- Missing layers — domains with application elements but no technology or business layer entries
- Undocumented relationships — elements with empty or TBD relationship fields
- Missing views — domains without any diagrams in
views/<domain>/ - Broken references — relationships pointing to non-existent elements
-
Output a health report:
Catalog Health
- Total elements: N
- Healthy (all required fields): N
- Connected (has relationships): N
- Orphans (no connections): N
- Domains: N (list)
Layer Distribution
Layer Count Gaps to Fill Next
Priority What Why Suggested Action 1 ... ... /new-entry ...or "Add relationship to ..." -
Suggest the top 5 things to document next, ranked by impact.
Rules
- Be concise — this is a quick health check, not a deep audit
- Prioritize by impact: broken refs > orphans > thin domains > missing views
- Always suggest concrete next steps (specific
/new-entrycommands or edits) - Orphan elements are normal for incomplete models — note them but don't alarm
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.
- 6d ago First seen · 58 lines · 52 tokens per session scan A 1fafc37a620a
health-advisor is an agent published in the GitHub repository ea-toolkit/architecture-catalog (38 stars, last pushed 4mo ago), licensed MIT. It adds 52 tokens to every session and 514 once invoked, about $0.0003 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
auto-reviewer
Automated PR reviewer for the EmDash CI workflows. Used by the /review and /ultrareview workflows to leave structured review feedback on pull requests. Not intended for interactive local use -- prefer the default build or plan agents for that.
discovery
How an agent finds these surfaces without being told: the API catalog, DNS-based discovery, an agent-skills index, and the places people actually look.
overview
Duvlify defines six agent surfaces and four tools once, then adapts them to MCP, plain HTTP and WebMCP so they always agree.
mcp
The page outline agents read for line offsets, the in-browser WebMCP bridge and when to run it yourself, the rate limits, and how the surfaces are tested.
lp-brandmark
Brandmark designer (LandingForge phase 3.5 — after lp-designer's tokens/design, before/with lp-builder). Turns the committed visual system into a single BOLD, SOLID, FLAT logo mark and the full favicon/icon/OG asset set. Reads design.md (accent hex, mood, light|dark base) + brief.md (product, positioning → mark…
router-agent
Scope: Single entrypoint agent for the Evolith BMAD ecosystem. It receives natural language prompts from users or systems, reads the .harness/manifest.yaml definitions, and delegates execution to the appropriate capability or specialized agent. Inputs: User prompt and the .harness/manifest.yaml file. Outputs: A strict…