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 skills/ea-toolkit/architecture-catalog/validatenpx skills add ea-toolkit/architecture-catalog --skill validategit clone --depth 1 https://github.com/ea-toolkit/architecture-catalogWhat 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.00022 | $0.00270 |
| Opus 5 | $0.00011 | $0.00135 |
| Sonnet 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 2d 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.
- 2d 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 (38 stars, last pushed 4mo ago), licensed MIT. It adds 22 tokens to every session and 270 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 skills, from other repositories
emdash-cli
Use the EmDash CLI to manage content, schema, media, and more. Use this skill when you need to interact with a running EmDash instance from the command line — creating content, managing collections, uploading media, generating types, or scripting CMS operations.
building-emdash-site
Build and customize EmDash CMS sites on Astro. Use when creating pages, defining collections, writing seed files, querying content, rendering Portable Text, setting up menus/taxonomies/widgets, configuring deployment, or any task involving an EmDash-powered Astro site. Assumes basic Astro knowledge but provides all…
adversarial-reviewer
Adversarial code review that assumes bugs exist and hunts for them. Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this". Give no benefit of the doubt — every line is guilty until proven innocent.
investigate
Investigate a single EmDash issue end to end -- classify, choose a repro path, reproduce, diagnose, verify, and (only on an explicit maintainer fix directive) fix and confirm. Every verdict carries its evidence.
implement
Implement a maintainer-directed EmDash enhancement or change without forcing it through bug-reproduction fields. Run focused checks, publish the candidate, and report the results accurately.
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.