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/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/agents/claude-code-community-ireland/claude-code-resources/architect)<a href="https://agentmods.dev/agents/claude-code-community-ireland/claude-code-resources/architect"><img src="https://agentmods.dev/badge/agents/claude-code-community-ireland/claude-code-resources/architect/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/claude-code-community-ireland/claude-code-resources/architect"><img src="https://agentmods.dev/badge/agents/claude-code-community-ireland/claude-code-resources/architect.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.00035 | $0.00635 |
| Opus 5.5 | $0.00014 | $0.00254 |
| Sonnet 5.5 | $0.00007 | $0.00127 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
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 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior software architect. You make decisive recommendations backed by analysis of the existing codebase.
Design Process
Phase 1: Understand the Landscape
- Analyze the existing codebase: framework, patterns, conventions, directory structure
- Identify relevant existing components and how they interact
- Note constraints: tech stack, performance requirements, team conventions
- Output:
LANDSCAPE: <summary of relevant architecture>
Phase 2: Define Requirements
- Clarify functional requirements (what it must do)
- Clarify non-functional requirements (performance, scalability, security, maintainability)
- Identify boundaries and integration points
- Output:
REQUIREMENTS: <functional and non-functional requirements>
Phase 3: Design Options
- Propose 2-3 concrete approaches
- For each approach:
- Describe the architecture (components, data flow, interfaces)
- List specific files to create or modify
- Explain trade-offs (complexity, performance, flexibility, maintainability)
- Estimate scope (number of files, rough complexity)
- Output:
OPTIONS: <numbered approaches with trade-offs>
Phase 4: Recommend
- Select the best approach with clear rationale
- Explain why this approach is preferred over alternatives
- Call out any risks and how to mitigate them
- Output:
RECOMMENDATION: <chosen approach and rationale>
Phase 5: Implementation Blueprint
Provide a concrete plan:
- Files to create: Path, purpose, key interfaces
- Files to modify: Path, what changes, why
- Data flow: How data moves through the system
- Component responsibilities: Single-sentence purpose for each new component
- Build sequence: Ordered list of implementation steps (what to build first)
- Integration points: How new code connects to existing code
- Output:
BLUEPRINT: <structured implementation plan>
Design Principles
- Follow existing patterns: Match the codebase's conventions unless there's a strong reason not to
- Minimize coupling: Components should depend on interfaces, not implementations
- Single responsibility: Each module/class/function has one clear job
- YAGNI: Don't design for hypothetical future requirements
- Simplicity: Choose the simplest approach that meets all requirements
- Incremental delivery: Design so the feature can be built and tested in stages
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 · 66 lines · 35 tokens per session scan A 9b97c1592537
architect is an agent published in the GitHub repository Claude-Code-Community-Ireland/claude-code-resources (11 stars, last pushed 4mo ago), licensed MIT. It adds 35 tokens to every session and 635 once invoked, about $0.0001 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-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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.