Borrowing it
Nothing to install: this file belongs to J-o-n-a-t-h-a-n-M-u-e-l-l-e-r/lattice. 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/J-o-n-a-t-h-a-n-M-u-e-l-l-e-r/lattice/main/.github/agents/mcp-engineer.agent.mdgit clone --depth 1 https://github.com/J-o-n-a-t-h-a-n-M-u-e-l-l-e-r/latticeWrote 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/j-o-n-a-t-h-a-n-m-u-e-l-l-e-r/lattice/mcp-engineer)<a href="https://agentmods.dev/agents/j-o-n-a-t-h-a-n-m-u-e-l-l-e-r/lattice/mcp-engineer"><img src="https://agentmods.dev/badge/agents/j-o-n-a-t-h-a-n-m-u-e-l-l-e-r/lattice/mcp-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/j-o-n-a-t-h-a-n-m-u-e-l-l-e-r/lattice/mcp-engineer"><img src="https://agentmods.dev/badge/agents/j-o-n-a-t-h-a-n-m-u-e-l-l-e-r/lattice/mcp-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.00040 | $0.00328 |
| Opus 5.5 | $0.00016 | $0.00131 |
| Sonnet 5.5 | $0.00008 | $0.00066 |
| Haiku 4.5 | $0.00004 | $0.00033 |
Grade A, and why
mcp-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 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 build the agent-facing half of Lattice: the MCP server in apps/backend/src/mcp/.
Read docs/04-mcp-surface.md.
The design principle
The graph is a shared, self-maintaining substrate. Anything that learns something puts it back.
There is no approval queue. report_dependency feeds an agent's discovery into the graph through the same validators and the same write threshold as model-inferred edges — never a privileged path that skips them. source: 'agent_reported', confidence 0.9, because an agent that hit a real wall is better evidence than a model reading titles.
All reads are served from the store — the same queries that back the REST API (docs/12-rest-api.md). An MCP tool must never trigger inference or call GitHub; five agents polling list_ready_work should cost five cache hits.
Not a GitHub wrapper
The official GitHub MCP server already exposes issue CRUD. Ours exposes the derived schedule, which exists nowhere else. If a tool you're adding could be replaced by a call to github-mcp-server, it doesn't belong here.
Build scripts/agent.ts early
It's a real MCP client that claims an issue, prints the briefing, and reports progress. It is simultaneously how you test the server and demonstrate the coordination loop.
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 · 40 tokens per session scan A 23cfe28d9c2f
mcp-engineer is an agent published in the GitHub repository J-o-n-a-t-h-a-n-M-u-e-l-l-e-r/lattice (0 stars, last pushed 2mo ago), licensed MIT. It adds 40 tokens to every session and 328 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.
mcp-engineer compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| mcp-engineerJ-o-n-a-t-h-a-n-M-u-e-l-l-e-r/lattice | Agent | 0 | 2mo ago | MIT | A | 40 | Claude Code |
| php-developerdavepoon/buildwithclaude | Agent | 3.7k | yesterday | MIT | A | 51 | Claude Code |
| backend-reviewerjeremylongshore/tons-of-skills-marketplace | Agent | 2.9k | yesterday | MIT | A | 36 | Claude Code |
| integrations-engineeravelikiy/great_cto | Agent | 112 | 2d ago | MIT | A | 106 | Claude Code |
| gatetonone-ai/tonone | Agent | 77 | 23d ago | MIT | A | 19 | Claude Code |
| broadcasting-agentSofttor/nestjs-hexagonal | Agent | 5 | 29d ago | MIT | A | 58 | Claude Code |
| dotnet-architecture-reviewerStefanTheCode/dotnet-ai-toolkit | Agent | 26 | 2mo ago | MIT | A | 102 | Claude Code |