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 Claude-Code-Community-Ireland/claude-code-resources --skill architecture-decision-recordgit clone --depth 1 https://github.com/Claude-Code-Community-Ireland/claude-code-resourcesWrote 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/claude-code-community-ireland/claude-code-resources/architecture-decision-record)<a href="https://agentmods.dev/skills/claude-code-community-ireland/claude-code-resources/architecture-decision-record"><img src="https://agentmods.dev/badge/skills/claude-code-community-ireland/claude-code-resources/architecture-decision-record/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/skills/claude-code-community-ireland/claude-code-resources/architecture-decision-record"><img src="https://agentmods.dev/badge/skills/claude-code-community-ireland/claude-code-resources/architecture-decision-record.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.00031 | $0.02483 |
| Opus 5.5 | $0.00012 | $0.00993 |
| Sonnet 5.5 | $0.00006 | $0.00497 |
| Haiku 4.5 | $0.00003 | $0.00248 |
Grade A, and why
architecture-decision-record scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Easy to test with curl, Postman, or any HTTP client How it starts
The opening of the file, as written. The whole thing — 350 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Decision Records
ADR Template
Every ADR follows this structure:
# ADR-NNN: Title of the Decision
## Status
[Proposed | Accepted | Deprecated | Superseded by ADR-NNN]
## Context
What is the issue that we are seeing that motivates this decision or change?
Describe the forces at play (technical, political, social, project-related).
Include any constraints, requirements, or assumptions.
## Decision
What is the change that we are proposing and/or doing?
State the decision in full sentences using active voice.
Be specific about what will be done.
## Consequences
What becomes easier or more difficult because of this decision?
List both positive and negative consequences.
Include any follow-up actions required.
When to Write an ADR
Write an ADR for any decision that meets one or more of these criteria:
| Trigger | Example |
|---|---|
| Adopting or replacing a technology | Switching from REST to GraphQL |
| Changing an architectural pattern | Moving from monolith to microservices |
| Infrastructure decisions | Choosing a cloud provider or database |
| API design choices | Choosing pagination strategy |
| Authentication/authorization strategy | Adopting OAuth2 with PKCE |
| Data model decisions | Choosing between SQL and NoSQL |
| Cross-cutting concerns | Standardizing error handling or logging |
| Process or convention changes | Adopting conventional commits |
| Build/deployment decisions | Choosing CI/CD platform |
| Decisions that are hard to reverse | Anything with significant migration cost |
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 · 350 lines · 31 tokens per session scan A 7d3e5c508a79
architecture-decision-record is a skill published in the GitHub repository Claude-Code-Community-Ireland/claude-code-resources (11 stars, last pushed 4mo ago), licensed MIT. It adds 31 tokens to every session and 2,483 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…