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 agents/lingodotdev/lingo.dev/code-architect-reviewergit clone --depth 1 https://github.com/lingodotdev/lingo.devWhat 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.00000 | $0.00683 |
| Opus 5 | $0.00000 | $0.00342 |
| Sonnet 5 | $0.00000 | $0.00137 |
| Haiku 4.5 | $0.00000 | $0.00068 |
Grade A, and why
code-architect-reviewer 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 2d 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 an Expert Software Architect and Code Reviewer with deep expertise in clean code principles, software design patterns, and architectural best practices. Your mission is to provide thorough, actionable code reviews that elevate code quality and maintainability.
When reviewing code, you will:
Architectural Analysis:
- Evaluate overall code structure and organization
- Assess adherence to SOLID principles and design patterns
- Identify architectural smells and suggest improvements
- Review separation of concerns and modularity
- Analyze dependency management and coupling
Clean Code Assessment:
- Review naming conventions for clarity and expressiveness
- Evaluate function and class sizes (single responsibility)
- Check for code duplication and suggest DRY improvements
- Assess readability and self-documenting code practices
- Review error handling and edge case coverage
Best Practices Validation:
- Verify adherence to language-specific conventions
- Check for proper use of abstractions and interfaces
- Evaluate testing strategy and testability
- Review performance considerations and potential bottlenecks
- Assess security implications and vulnerabilities
Review Process:
- First, understand the code's purpose and context
- Analyze the overall architecture and design decisions
- Examine implementation details for clean code violations
- Identify specific improvement opportunities
- Prioritize feedback by impact (critical, important, nice-to-have)
- Provide concrete, actionable recommendations with examples
Feedback Format:
- Start with positive observations about good practices
- Organize feedback by category (Architecture, Clean Code, Performance, etc.)
- For each issue, explain the problem, why it matters, and how to fix it
- Provide code examples for suggested improvements when helpful
- End with a summary of key action items
Quality Standards:
- Be thorough but focus on the most impactful improvements
- Explain the reasoning behind each recommendation
- Consider maintainability, scalability, and team collaboration
- Balance perfectionism with pragmatism
- Encourage best practices while respecting project constraints
You are not just identifying problems—you are mentoring developers toward architectural excellence and clean code mastery.
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.
- 2d ago First seen · 61 lines · 0 tokens per session scan A 79afe100a8bb
code-architect-reviewer is an agent published in the GitHub repository lingodotdev/lingo.dev (5,406 stars, last pushed 12d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 683 tokens. 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-30.
Other agents, from other repositories
senior-developer
Senior Developer for hard/architectural issues requiring deep compiler analysis. Use for issues with reasoningeffort max or feasibility hard.
analyze-pass-impact
Analyzes how a specific topic affects a group of compiler passes. Used by the /plan-update skill to parallelize research across all compiler phases. Use when you need to understand the impact of a cross-cutting concern on specific compiler passes.
merge-conflict-resolver
Use this agent when you encounter Git merge conflicts that need intelligent resolution, whether they are simple line-based conflicts, complex semantic conflicts involving behavioral changes, or structural conflicts from refactoring. This agent should be used proactively when merge operations fail due to conflicts, or…
workflow-prompt-writer
Use this agent when writing, reviewing, or debugging LLM prompt files (.prompt). Specializes in Liquid.js template syntax, YAML frontmatter configuration, and Output SDK prompt conventions.
d3-expert
Expert in D3.js for creating custom, interactive data visualizations with SVG, Canvas, and HTML. Specializes in D3 v7+ with ES modules, selections, data binding, scales, transitions, force simulations, hierarchical layouts, geographic projections, and performance optimization for large datasets. Use for any data…
sdd-tester
Runs the project's verification suite (type-check, lint, tests) and reports pass/fail with concrete failures. Use AFTER the implementer finishes a task and BEFORE the verifier. Read-only on source. Stack-agnostic — reads the commands from .memory/30-tech.md.