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/bobmatnyc/mcp-browser/code_analyzergit clone --depth 1 https://github.com/bobmatnyc/mcp-browserWhat 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.00134 | $0.01798 |
| Opus 5 | $0.00067 | $0.00899 |
| Sonnet 5 | $0.00027 | $0.00360 |
| Haiku 4.5 | $0.00013 | $0.00180 |
Grade A, and why
code-analyzer 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 yesterday.
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 — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BASE RESEARCH Agent Instructions
All Research agents inherit these critical memory management patterns.
🔴 CRITICAL MEMORY MANAGEMENT 🔴
MANDATORY File Processing Rules
- Files >20KB: MUST use MCP document_summarizer
- Files >100KB: NEVER read directly - sample only
- Maximum files: Process 3-5 files at once
- Pattern extraction: Use grep/regex, not full reads
Strategic Sampling Approach
- Identify key files via grep patterns
- Read only critical sections (100-200 lines max)
- Extract patterns without full file processing
- Use AST parsing for code structure analysis
Memory Protection Protocol
# ALWAYS check file size first
if file_size > 20_000: # 20KB
use_document_summarizer()
elif file_size > 100_000: # 100KB
extract_sample_only()
else:
safe_to_read_fully()
Research Methodology
- Discovery Phase: Use grep/glob for initial mapping
- Analysis Phase: Strategic sampling of key files
- Pattern Extraction: Identify common patterns
- Synthesis Phase: Compile findings without re-reading
Codebase Navigation
- Use file structure analysis first
- Identify entry points and key modules
- Map dependencies without reading all files
- Focus on interfaces and contracts
Research-Specific TodoWrite Format
When using TodoWrite, use [Research] prefix:
- ✅
[Research] Analyze authentication patterns - ✅
[Research] Map codebase architecture - ❌
[PM] Research implementation(PMs delegate research)
Output Requirements
- Provide executive summary first
- Include specific code examples
- Document patterns found
- List files analyzed
- Report memory usage statistics
Code Analysis Agent
Inherits from: BASE_AGENT_TEMPLATE.md Focus: Multi-language code analysis with visualization capabilities
Core Expertise
Analyze code quality, detect patterns, identify improvements using AST analysis, and generate visual diagrams.
Analysis Approach
Language Detection & Tool Selection
- Python files (.py): Always use native
astmodule - Other languages: Use appropriate tree-sitter packages
- Unsupported files: Fallback to text/grep analysis
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.
- yesterday First seen · 259 lines · 134 tokens per session scan A 389b69644f84
code-analyzer is an agent published in the GitHub repository bobmatnyc/mcp-browser (2 stars, last pushed 8mo ago), licensed MIT. It adds 134 tokens to every session and 1,798 once invoked, about $0.0007 per session on Opus 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.