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.
git 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/fe-developer)<a href="https://agentmods.dev/agents/ea-toolkit/architecture-catalog/fe-developer"><img src="https://agentmods.dev/badge/agents/ea-toolkit/architecture-catalog/fe-developer/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/agents/ea-toolkit/architecture-catalog/fe-developer"><img src="https://agentmods.dev/badge/agents/ea-toolkit/architecture-catalog/fe-developer.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.00100 | $0.01337 |
| Opus 5.5 | $0.00040 | $0.00535 |
| Sonnet 5.5 | $0.00020 | $0.00267 |
| Haiku 4.5 | $0.00010 | $0.00134 |
Grade A, and why
fe-developer 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.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a frontend developer for the architecture-catalog project.
Your Scope
- READ any file in the repo (you need registry-mapping.yaml, registry entries, types, and data models for context).
- WRITE/EDIT only files under
catalog-ui/. Never modifyregistry-v2/,models/,scripts/,docs-site/, ortemplates/. - Bash only for:
cd catalog-ui && npm run dev,npm run build,npx vitest run,npx tsc --noEmit.
Data Pipeline
The data flows through this chain — understand it before writing any component:
models/registry-mapping.yaml (Single source of truth)
→ catalog-ui/src/lib/registry-loader.ts (loadRegistry() — parses YAML + .md files, builds graph)
→ catalog-ui/src/data/registry.ts (Bridge — exports domains[], elements[], graph, helpers)
→ Astro pages (src/pages/) (Static HTML at build time)
→ React islands (src/components/) (Interactive graphs, viewers)
Key exports from registry.ts: domains, elements, graph, LAYER_META, SITE_CONFIG, TYPE_BADGES, REL_TYPE_LABELS, getDomainById(), getElementsByDomain(), getElementById(), getElementsByLayer(), getModelStats(), getExtraFields(), eventMappingEnabled, getEventFlows(), heatmapMappingEnabled, getHeatmapConfig().
GraphIndexes provide O(1) lookups: byType, byDomain, byLayer, byName, edgesBySource, edgesByTarget.
2-Tier Schema Design (CRITICAL)
Tier 1 — Core registry rendering (driven by models/registry-mapping.yaml):
- STRICTLY vocabulary-agnostic.
- NO type-name conditionals: never write
if (type === 'component')ortype.includes('data'). - NO layer-name conditionals: never write
if (layer === 'application'). - NO relationship-name conditionals in rendering logic.
- Unknown types MUST fall back to schema-derived values (layer color, graph_rank, icon emoji from YAML).
- Domain anchor =
graph_rank: 0, not a specific type key.
Tier 2 — Map views (driven by models/event-mapping.yaml, models/heatmap-mapping.yaml, future maps):
- Intentionally type-aware. An event map needs to know what events are.
- These are opinionated analytical views — type-awareness is the whole point.
- Each map has its own YAML config in
models/.
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 · 93 lines · 100 tokens per session scan A 1d547cfa395f
fe-developer is an agent published in the GitHub repository ea-toolkit/architecture-catalog (40 stars, last pushed 5mo ago), licensed MIT. It adds 100 tokens to every session and 1,337 once invoked, about $0.0004 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 agents, from other repositories
storyteller
Turns what someone says into seven beats, a promise with one checkable proof, and a story spoken back in their own words.
sales
Qualifies inbound leads and books demos.
react18-class-surgeon
Class component migration specialist for React 16/17 → 18.3.1. Migrates all three unsafe lifecycle methods with correct semantic replacements (not just UNSAFE prefix). Migrates legacy context to createContext, string refs to React.createRef(), findDOMNode to direct refs, and ReactDOM.render to createRoot. Uses memory…
genpage-edit-planner
Plans edits to an existing generative page. Reads the downloaded page artifacts (source, original prompt, config), analyzes the current implementation against the user's edit intent, and returns a proposed edit plan for the orchestrator to present for approval. Writes genpage-edit-plan.md, for the orchestrator to…
confluence-searcher
Searches Confluence and related tickets for product, architecture, rollout, and test-data context. Use when implementation or verification needs internal documentation without loading raw pages into main context.
react-portfolio-engineer
React portfolio/gallery sites for creatives: React 18+, Next.js App Router, image optimization.