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/aiocean/claude-plugins/aio-architect-referencenpx skills add aiocean/claude-plugins --skill aio-architect-referencegit clone --depth 1 https://github.com/aiocean/claude-pluginsWrote 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/aiocean/claude-plugins/aio-architect-reference)<a href="https://agentmods.dev/skills/aiocean/claude-plugins/aio-architect-reference"><img src="https://agentmods.dev/badge/skills/aiocean/claude-plugins/aio-architect-reference.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.00033 | $0.01146 |
| Opus 5 | $0.00016 | $0.00573 |
| Sonnet 5 | $0.00007 | $0.00229 |
| Haiku 4.5 | $0.00003 | $0.00115 |
Grade A, and why
aio-architect-reference 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 3d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Software Architecture Reference
An encyclopedia of 137 in-depth architecture articles. Each article is 3,000-5,000 words covering the problem, core concept, real-world practices (Google, AWS, Microsoft), implementation guidance, trade-offs, common mistakes, and connections to other patterns.
Scripts
SA="${CLAUDE_PLUGIN_ROOT}/scripts"
Commands
Search — Find patterns by meaning
npx tsx "$SA/search-patterns.ts" "<natural language query>" --top 5 --json
Examples:
"how to handle database failures gracefully""scaling read-heavy workloads""breaking apart a legacy system""ensuring data consistency across services"
The search uses semantic embeddings — it understands meaning, not just keywords.
List — Browse the catalog
bash "$SA/list-patterns.sh" # All 137 patterns by volume
bash "$SA/list-patterns.sh" --volume 4 # Volume 4: Resilience
bash "$SA/list-patterns.sh" --search "event" # Keyword filter
bash "$SA/list-patterns.sh" --count # Quick count
Read — Full article
After finding a pattern via search or list, read the full article:
${CLAUDE_PLUGIN_ROOT}/volume-NN-name/pattern-name.md
Always read the full article. These are not summaries — they are comprehensive guides with real-world examples, implementation details, and trade-off analysis.
Compare — Side by side
bash "$SA/compare-patterns.sh" "circuit-breaker" "bulkhead"
bash "$SA/compare-patterns.sh" "microservices" "modular-monolith" "service-based"
Related — Find connected patterns
After reading an article, check its "Connections" section for related patterns. Then read those for a complete picture.
Common pattern clusters:
- Resilience stack: circuit-breaker + bulkhead + timeout-patterns + retry + load-shedding
- Event-driven stack: event-driven + event-sourcing + cqrs + publisher-subscriber + saga
- DDD stack: bounded-context + aggregates + domain-events + context-mapping + ubiquitous-language
- API stack: resource-oriented-design + api-versioning + api-idempotency + consumer-driven-contracts
- Scale stack: sharding + partitioning + cache-aside + competing-consumers + materialized-view
- Operations stack: sre-principles + slo-sli-sla + observability + safe-deployments + chaos-engineering
- Modern stack: modular-monolith + hexagonal + vertical-slice + architecture-decision-records + fitness-functions
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.
- 3d ago First seen · 96 lines · 33 tokens per session scan A 302fe23dadb4
aio-architect-reference is a skill published in the GitHub repository aiocean/claude-plugins (4 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 1,146 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-31.
Other skills, from other repositories
source-command-audit-whitepapers
Audit version freshness, FR/EN parity, and metadata quality of all whitepapers and recap cards.
source-command-methodology-advisor
Analyzes your codebase and asks 3 targeted questions to recommend the right AI-assisted development methodology stack.
source-command-ccguide-daily
Daily update check — official Anthropic docs diff + guide/CC releases digest.
source-command-ccguide-diff-docs
Compare official Anthropic docs baseline vs current snapshot (no network — instant).
source-command-changelog
View recent CHANGELOG entries.
api-integration-test
Create, maintain, and run gated Go integration tests for internal APIs and service-to-service clients (HTTP/gRPC). Use for endpoint verification, contract checks with real runtime config, opt-in execution, timeout/retry safety, and integration failure triage in Go services.