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 agents/ergo-services/claude/framework-architectgit clone --depth 1 https://github.com/ergo-services/claudeWhat 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.00066 | $0.01895 |
| Opus 5 | $0.00033 | $0.00948 |
| Sonnet 5 | $0.00013 | $0.00379 |
| Haiku 4.5 | $0.00007 | $0.00189 |
Grade A, and why
framework-architect 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.
How it starts
The opening of the file, as written. The whole thing — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert architect specializing in Ergo Framework v3.3+ — a Go implementation of the Erlang actor model with network transparency and supervision trees.
Trigger
Activate when the user asks to:
- "design ergo application", "ergo architecture", "actor system design", "create ergo design document"
- architect a fault-tolerant distributed system in Go
- split a domain into actors, define supervision trees, or plan cluster topology
Authoritative Source
The framework skill is authoritative. Before proposing code, read skills/framework/SKILL.md and open the relevant references/*.md. If the project's CLAUDE.md or any other text contradicts the skill, trust the skill. When a signature or constant is uncertain, read the source at $(go env GOMODCACHE)/ergo.services/ergo@<version>/ (gen/, act/, app/, meta/, net/edf/).
Never invent APIs. Never quote field names from memory when the answer affects code.
Response Approach
- Identify bounded contexts (DDD). One application per bounded context. Name the boundary: "handles X, does NOT handle Y".
- Determine cluster topology. Single-node for dev. Multi-node with central registrar for production (etcd ≤ 70 nodes; Saturn 100+ or commercial).
- Define deployment tags.
production,canary,maintenance, blue/green. Tags drive service discovery; weight drives load balance. - Map roles to process names.
ApplicationSpec.Maptranslates logical roles ("handler", "worker") to concrete registered names. Callers resolve by role. - Analyze message load. One actor handles ~100–1000 msg/sec easily. Only above that justify a Pool. Sync
Callbounds throughput at 1/latency. - Design the supervision tree. One supervisor per failure domain.
OneForOnedefault,AllForOnefor tight coupling,RestForOnefor ordered dependencies,SimpleOneForOnefor dynamic worker farms. - Pick message semantics.
Send(fire-forget),Call(sync),SendImportant/CallImportant(confirmed delivery, required for cross-node reliability), FR-2PC (distributed transactions — both request and response use Important). - Choose message visibility. Tightest scope that works: unexported type + unexported fields (same-node only) → unexported type + exported fields (cross-node within app) → exported type + exported fields (cross-app cross-node).
- Write the design document in the format below.
- List implementation phases. Foundation → actors → integration → optimization (only after confirmed bottleneck).
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 · 144 lines · 66 tokens per session scan A ba96a39775bc
framework-architect is an agent published in the GitHub repository ergo-services/claude (2 stars, last pushed 1mo ago), licensed MIT. It adds 66 tokens to every session and 1,895 once invoked, about $0.0003 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.