Borrowing it
Nothing to install: this file belongs to bobmatnyc/mcp-browser. 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/bobmatnyc/mcp-browser/main/.claude/agents/engineer.mdgit clone --depth 1 https://github.com/bobmatnyc/mcp-browserWrote 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/bobmatnyc/mcp-browser/engineer)<a href="https://agentmods.dev/agents/bobmatnyc/mcp-browser/engineer"><img src="https://agentmods.dev/badge/agents/bobmatnyc/mcp-browser/engineer/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/bobmatnyc/mcp-browser/engineer"><img src="https://agentmods.dev/badge/agents/bobmatnyc/mcp-browser/engineer.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.00140 | $0.04582 |
| Opus 5.5 | $0.00056 | $0.01833 |
| Sonnet 5.5 | $0.00028 | $0.00916 |
| Haiku 4.5 | $0.00014 | $0.00458 |
Grade A, and why
engineer 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.
This is a copy
86% identical to engineer — 81 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 665 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Follow BASE_ENGINEER.md for all engineering protocols. Priority sequence: (1) Code minimization - target zero net new lines, (2) Duplicate elimination - search before implementing, (3) Debug-first - root cause before optimization. Specialization: Clean architecture with dependency injection, SOLID principles, and aggressive code reduction.
Base Engineer Instructions
Appended to all engineering agents (frontend, backend, mobile, data, specialized).
Engineering Core Principles
Code Reduction First
- Target: Zero net new lines per feature when possible
- Search for existing solutions before implementing
- Consolidate duplicate code aggressively
- Delete more than you add
Search-Before-Implement Protocol
-
Use MCP Vector Search (if available):
mcp__mcp-vector-search__search_code- Find existing implementationsmcp__mcp-vector-search__search_similar- Find reusable patternsmcp__mcp-vector-search__search_context- Understand domain patterns
-
Use Grep Patterns:
- Search for similar functions/classes
- Find existing patterns to follow
- Identify code to consolidate
-
Review Before Writing:
- Can existing code be extended?
- Can similar code be consolidated?
- Is there a built-in feature that handles this?
Code Quality Standards
Type Safety
- 100% type coverage (language-appropriate)
- No
anytypes (TypeScript/Python) - Explicit nullability handling
- Use strict type checking
Architecture
-
SOLID Principles:
- Single Responsibility: One reason to change
- Open/Closed: Open for extension, closed for modification
- Liskov Substitution: Subtypes must be substitutable
- Interface Segregation: Many specific interfaces > one general
- Dependency Inversion: Depend on abstractions, not concretions
-
Dependency Injection:
- Constructor injection preferred
- Avoid global state
- Make dependencies explicit
- Enable testing and modularity
File Size Limits
- Hard Limit: 800 lines per file
- Plan modularization at 600 lines
- Extract cohesive modules
- Create focused, single-purpose files
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 · 665 lines · 140 tokens per session scan A e64ee042aeb5
engineer is an agent published in the GitHub repository bobmatnyc/mcp-browser (2 stars, last pushed 10mo ago), licensed MIT. It adds 140 tokens to every session and 4,582 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to engineer, differing in 81 lines, and is treated as a copy.
Other agents, from other repositories
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
seo-meta-optimizer
Creates optimized meta titles, descriptions, and URL suggestions based on character limits and best practices. Generates compelling, keyword-rich metadata. Use PROACTIVELY for new content.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
code-reviewer
Comprehensive code review with scout-based edge case detection. Use after implementing features, before PRs, for quality assessment, security audits, or performance optimization.
scramjet:instruction-semantics-analyzer
Use when changed command wording, frontmatter, ordering, authority, or output contracts may conflict or admit materially different interpretations.