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/new-entrynpx skills add ea-toolkit/architecture-catalog --skill new-entrygit 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/new-entry)<a href="https://agentmods.dev/skills/ea-toolkit/architecture-catalog/new-entry"><img src="https://agentmods.dev/badge/skills/ea-toolkit/architecture-catalog/new-entry.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 | $0.00031 | $0.00612 |
| Opus 5 | $0.00015 | $0.00306 |
| Sonnet 5 | $0.00006 | $0.00122 |
| Haiku 4.5 | $0.00003 | $0.00061 |
Grade A, and why
new-entry 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 4d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create New Registry Entry
Guide the user through creating a properly structured registry entry.
Arguments
$1- Element type: component, software-system, data-concept, data-aggregate, data-entity, domain-event, api-endpoint, etc.$2+- Element name (can have spaces)
If arguments not provided, ask the user:
- What type of element?
- What is the element name?
- Which domain does it belong to?
Element Type to Folder Mapping
Do NOT hardcode paths. Always discover dynamically:
- Read
models/registry-mapping.yaml - Find the element type under
elements: - Use the
folder:field for that type to determine the target directory - Prepend
registry-v2/to the folder path
This ensures the skill works even if users rename layers, types, or restructure folders.
Workflow
- Determine element type and target folder
- Read
_template.mdin the target folder for structure - Read 1-2 existing entries in target folder for pattern reference
- Create filename: kebab-case of name (e.g., "Payment Record" -> "payment-record.md")
- Fill frontmatter:
- name: [provided name]
- owner: TBD
- status: draft
- [type-specific fields and relationships from template]
- Write file to correct folder
- Run validation:
python scripts/validate.py
Response Format
**Created:** registry-v2/<layer>/<type-folder>/element-name.md
**Frontmatter:**
---
type: <element-type>
name: <Element Name>
owner: TBD
status: draft
<type-specific fields from template>
---
**Next Steps:**
1. Fill in TBD fields
2. Add description in the body
3. Run /validate to verify
Would you like me to help fill in any of the TBD fields?
Domain-Specific Fields
For data elements (concepts, aggregates, entities), also include:
- Relationship to parent element (data concept -> aggregate -> entity chain)
- classification: internal/business-confidential/pii
For software elements (systems, subsystems), also include:
- sourcing: in-house/vendor/hybrid
- vendor: (if vendor)
- realizes_component: Which component this system supports
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.
- 4d ago First seen · 86 lines · 0 tokens per session scan A 96f6ddfd3466
new-entry is a skill published in the GitHub repository ea-toolkit/architecture-catalog (38 stars, last pushed 4mo ago), licensed MIT. It adds 31 tokens to every session and 612 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.
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.
repro-public
Reproduce a bug in the public-facing rendered site (not the admin). Attach a container, start the demo dev server, drive public routes with agent-browser, and capture the reproduction as screenshots plus a replayable transcript.