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 skills add ea-toolkit/architecture-catalog --skill validategit 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/skills/ea-toolkit/architecture-catalog/validate)<a href="https://agentmods.dev/skills/ea-toolkit/architecture-catalog/validate"><img src="https://agentmods.dev/badge/skills/ea-toolkit/architecture-catalog/validate/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/skills/ea-toolkit/architecture-catalog/validate"><img src="https://agentmods.dev/badge/skills/ea-toolkit/architecture-catalog/validate.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.00022 | $0.00270 |
| Opus 5.5 | $0.00009 | $0.00108 |
| Sonnet 5.5 | $0.00004 | $0.00054 |
| Haiku 4.5 | $0.00002 | $0.00027 |
Grade A, and why
validate 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 1mo 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
Validate Architecture Model
Run the validation script and interpret results for the user.
Workflow
- Run:
python scripts/validate.py - Parse the output
- Summarize for the user:
- Total elements in registry
- Validation errors (elements in diagrams but not registered)
- Orphan elements (registered but not in any diagram)
- Domain maturity scores
Response Format
**Validation Results**
| Metric | Count |
|--------|-------|
| Registry entries | X |
| Validation errors | X |
| Orphan elements | X |
**Errors (if any):**
[List each error with file location]
**Orphans by layer:**
[Group orphans by ArchiMate layer]
**Recommendations:**
[Suggest fixes for errors, note that orphans are expected for incomplete models]
Notes
- Orphan elements are normal for incomplete models - don't alarm the user
- Validation errors are more serious - these indicate diagrams reference unregistered elements
- If user asks for JSON output, run:
python scripts/validate.py --format json
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.
- 1mo ago First seen · 47 lines · 22 tokens per session scan A 3ad6c4c80b14
validate is a skill published in the GitHub repository ea-toolkit/architecture-catalog (40 stars, last pushed 5mo ago), licensed MIT. It adds 22 tokens to every session and 270 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-30.
Other skills, from other repositories
agent-browser
Use the agent-browser CLI to exercise web interfaces, inspect rendered accessibility state, verify interactions, and capture screenshots. Use for browser-based UI testing and evidence collection. Do not use as a substitute for deterministic Playwright coverage when an automated regression test is the requested…
ux-acceptance-tester
Perform a goal-driven, black-box UX acceptance journey in a browser and report the path, friction, and observable outcome. Use only in an isolated tester context with a supplied start URL and brief.
ux-acceptance-coordinator
Coordinate black-box, agent-driven UX acceptance journeys against a disposable EmDash admin site. Use when preparing, dispatching, verifying, or reporting a manual browser journey performed by a separate tester agent. Do not use for deterministic Playwright tests or ordinary code review.
repro-api
Reproduce an EmDash bug below the browser layer -- REST handlers, CLI, MCP, migrations, schema registry, or build tooling. No browser. Prefer a failing vitest test in the affected package, run in an attached container.
adversarial-reviewer
Stress-test a code change for concrete correctness defects, unsafe assumptions, and failure modes. Use when the user explicitly asks for an adversarial review, a deep bug hunt, or to tear a change apart, or to check your own change before submitting it. Do not use for ordinary review, style feedback, or general…
work
Deliver one maintainer-approved EmDash issue, choosing the bug-fix path for a defect and the direct implementation path for an enhancement or task.