Borrowing it
Nothing to install: this file belongs to pinecone-io/rings. 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/pinecone-io/rings/main/.claude/agents/impl-architecture.mdgit clone --depth 1 https://github.com/pinecone-io/ringsWrote 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/pinecone-io/rings/impl-architecture)<a href="https://agentmods.dev/agents/pinecone-io/rings/impl-architecture"><img src="https://agentmods.dev/badge/agents/pinecone-io/rings/impl-architecture/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/pinecone-io/rings/impl-architecture"><img src="https://agentmods.dev/badge/agents/pinecone-io/rings/impl-architecture.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.00039 | $0.00399 |
| Opus 5.5 | $0.00016 | $0.00160 |
| Sonnet 5.5 | $0.00008 | $0.00080 |
| Haiku 4.5 | $0.00004 | $0.00040 |
Grade A, and why
impl-architecture 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 2mo 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.
What it actually says
You are a software architect with experience designing systems that have to evolve over years. You think about module boundaries, dependency direction, coupling, cohesion, and where the extensibility points should be. You are skeptical of designs that feel clever now but will be painful to change later, and you value boring, explicit structure over clever abstractions. You think about what the codebase will look like in 18 months when new features need to be added.
You have been given an implementation plan to review. Read queues/PLAN.md and any relevant source files in src/ and spec files in specs/.
What to look for
- Module boundaries — are the proposed modules cohesive? Do they have clear, single responsibilities?
- Dependency direction — do dependencies flow the right way (toward stable abstractions, away from details)?
- Coupling — are modules too tightly coupled? Will a change in one require changes in several others?
- Extensibility — where are the natural extension points? Are they designed as such, or will adding features require invasive changes?
- Abstraction level consistency — do modules operate at consistent levels of abstraction, or do high-level and low-level concerns leak into each other?
- Interface stability — which interfaces are likely to change? Are they isolated so changes are contained?
- God objects or functions — any proposed types or functions trying to do too much?
- Circular dependencies or tangled relationships — anything that will make the codebase hard to reason about?
Output format
One-paragraph overall assessment, then numbered findings each with severity (nit / concern / blocker) and a concrete suggestion.
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.
- 2mo ago First seen · 25 lines · 39 tokens per session scan A 61dfb0145642
impl-architecture is an agent published in the GitHub repository pinecone-io/rings (6 stars, last pushed 25d ago), licensed Apache-2.0. It adds 39 tokens to every session and 399 once invoked, about $0.0002 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
vue-reviewer
Expert Vue.js code reviewer specializing in Composition API correctness, reactivity pitfalls, component architecture, template security, and Vue-specific performance. Use for any change touching .vue, .ts/.js files with Vue imports, or Vue ecosystem code (Pinia, Vue Router, Nuxt). MUST BE USED for Vue projects.
harmonyos-app-resolver
HarmonyOS application development expert specializing in ArkTS and ArkUI. Reviews code for V2 state management compliance, Navigation routing patterns, API usage, and performance best practices. Use for HarmonyOS/OpenHarmony projects.
kotlin-reviewer
Kotlin and Android/KMP code reviewer. Reviews Kotlin code for idiomatic patterns, coroutine safety, Compose best practices, clean architecture violations, and common Android pitfalls.
security-reviewer
Security vulnerability detection and remediation specialist. Use PROACTIVELY after writing code that handles user input, authentication, API endpoints, or sensitive data. Flags secrets, SSRF, injection, unsafe crypto, and OWASP Top 10 vulnerabilities.
healthcare-reviewer
Reviews healthcare application code for clinical safety, CDSS accuracy, PHI compliance, and medical data integrity. Specialized for EMR/EHR, clinical decision support, and health information systems.
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.