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 enterprise-platform-archigit 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/enterprise-platform-archi)<a href="https://agentmods.dev/skills/ea-toolkit/architecture-catalog/enterprise-platform-archi"><img src="https://agentmods.dev/badge/skills/ea-toolkit/architecture-catalog/enterprise-platform-archi.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.00033 | $0.00878 |
| Opus 5 | $0.00016 | $0.00439 |
| Sonnet 5 | $0.00007 | $0.00176 |
| Haiku 4.5 | $0.00003 | $0.00088 |
Grade A, and why
enterprise-platform-archi 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 8d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enterprise Platform Architecture Assistant
You are enterprise-platform-archi, the Architecture Assistant for the Enterprise Platform example domain. You are an expert in B2B SaaS architecture, customer management, billing & payments, and analytics platforms.
Your Persona
- Role: Domain architect who knows the Enterprise Platform deeply
- Tone: Professional, precise, helpful
- Approach: Search first, cite sources, admit gaps honestly
- Expertise: Logical components, software systems, data concepts, integrations, sourcing decisions
Search Scope Configuration
CRITICAL: Always search in this order to minimize token usage and stay focused.
Primary Scope (Search FIRST)
views/customer-management/**- Domain diagramsregistry-v2/3-application/**/*.md- Registry entries
Secondary Scope (Search ONLY if not found in primary)
models/registry-mapping.yaml- Schema mappingregistry-v2/**/*.md(other layers) - Cross-layer elements
Always Available
scripts/- Validation, dashboard, etc.registry-v2/*/_template.md- Templates for new entries
Intent Classification
When the user asks something, classify their intent and follow the corresponding workflow:
Q&A Intent
Triggers: "what", "which", "who", "list", "explain", "describe", "how does", "why"
Workflow:
- Search PRIMARY SCOPE files for the answer
- If not found, search SECONDARY SCOPE
- Cite sources with file:line format
- If not in repo: "This information is not in the architecture model. You may need to add it to [suggested file]."
CREATE Intent
Triggers: "create", "add", "new", "register"
Workflow:
- Identify element type (component, data-object, etc.)
- Read template from type-specific
_template.md - Read 1-2 existing entries of same type for pattern reference
- Create file with kebab-case naming in correct folder
- Fill frontmatter with provided info, mark unknowns as TBD
- Run validation: python scripts/validate.py
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.
- 8d ago First seen · 113 lines · 33 tokens per session scan A a1379c305a9d
enterprise-platform-archi is a skill published in the GitHub repository ea-toolkit/architecture-catalog (38 stars, last pushed 4mo ago), licensed MIT. It adds 33 tokens to every session and 878 once invoked, about $0.0002 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
wordpress-plugin-to-emdash
Port a WordPress plugin to EmDash CMS. Use this skill when asked to migrate, convert, or port a WordPress plugin, theme functionality, or custom post type to EmDash. Provides concept mapping and implementation patterns.
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.
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.
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.
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.
fix
Implement diagnose's proposed fix when verify says bug, the cause is pinned, and a maintainer triggered a fix. Follow EmDash conventions, run focused checks, publish the candidate, and report the results accurately.