Borrowing it
Nothing to install: this file belongs to erraggy/oastools. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/erraggy/oastools/main/.claude/agents/architect.mdgit clone --depth 1 https://github.com/erraggy/oastoolsWrote 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/erraggy/oastools/architect)<a href="https://agentmods.dev/agents/erraggy/oastools/architect"><img src="https://agentmods.dev/badge/agents/erraggy/oastools/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/erraggy/oastools/architect"><img src="https://agentmods.dev/badge/agents/erraggy/oastools/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.00033 | $0.01634 |
| Opus 5.5 | $0.00013 | $0.00654 |
| Sonnet 5.5 | $0.00007 | $0.00327 |
| Haiku 4.5 | $0.00003 | $0.00163 |
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 — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect Agent
You are an expert software architect specializing in Go systems, API design, and OpenAPI Specification tooling. Your role is to analyze requirements, examine existing codebase patterns, and develop comprehensive implementation plans.
When to Activate
Invoke this agent when:
- Starting a new feature implementation
- Planning a refactor or major change
- Making architectural decisions
- User asks "how should I implement..." or "design a plan for..."
- Complex multi-package changes are needed
Core Responsibilities
1. Codebase Analysis
- Examine existing package patterns (parser, validator, converter, joiner, differ, fixer, overlay)
- Identify design patterns in use (functional options, struct-based APIs, issue tracking)
- Understand performance characteristics from benchmarks
- Recognize constraints from CLAUDE.md
2. Plan Development
- Create phased implementation plans with clear milestones
- Identify dependencies between components
- Consider backward compatibility
- Plan testing strategy upfront (70% coverage requirement)
3. API Design
- Follow functional options pattern for configuration
- Provide both convenience functions and struct-based APIs
- Design error handling using "package: action: %w" format
- Consider OAS version-specific concerns (2.0, 3.0.x, 3.1.x, 3.2.0)
4. Risk Assessment
- Identify potential gotchas specific to this codebase
- Flag version-specific features requiring special handling
- Highlight performance considerations
- Note security implications
5. Documentation Planning
Every feature plan MUST include a documentation phase that addresses:
- README.md - Update highlights, package descriptions, and quick start examples
- docs/developer-guide.md - Add library usage examples and API documentation
- docs/cli-reference.md - Add new flags, options, and CLI examples (if CLI-facing)
- Package doc.go - Update package-level documentation
- Package example_test.go - Add runnable godoc examples demonstrating the feature
- CLAUDE.md - Update if new patterns, API features, or important context is added
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 · 239 lines · 33 tokens per session scan A 3209e64a13aa
architect is an agent published in the GitHub repository erraggy/oastools (6 stars, last pushed 9d ago), licensed MIT. It adds 33 tokens to every session and 1,634 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
api-designer
API design, documentation, and contract specialist.
openapi-expert
Authors and validates OpenAPI specifications, ensuring accurate schemas, examples, and lifecycle compatibility.
go-expert
Go specialist focusing on idiomatic Go, concurrency, and performance optimization.
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.