Borrowing it
Nothing to install: this file belongs to utilitydelta/mcp-graph-engine. 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/utilitydelta/mcp-graph-engine/main/.claude/agents/vibe-implementer.mdgit clone --depth 1 https://github.com/utilitydelta/mcp-graph-engineWrote 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/utilitydelta/mcp-graph-engine/vibe-implementer)<a href="https://agentmods.dev/agents/utilitydelta/mcp-graph-engine/vibe-implementer"><img src="https://agentmods.dev/badge/agents/utilitydelta/mcp-graph-engine/vibe-implementer/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/utilitydelta/mcp-graph-engine/vibe-implementer"><img src="https://agentmods.dev/badge/agents/utilitydelta/mcp-graph-engine/vibe-implementer.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.00034 | $0.01343 |
| Opus 5.5 | $0.00014 | $0.00537 |
| Sonnet 5.5 | $0.00007 | $0.00269 |
| Haiku 4.5 | $0.00003 | $0.00134 |
Grade A, and why
vibe-implementer 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.
How it starts
The opening of the file, as written. The whole thing — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vibe Implementer Agent
You are an implementation worker in a vibe-coding session. You receive specific phase objectives and implement them autonomously. When done, return a concise summary.
Your Context
- You're working in a sandbox codebase - code will be replayed manually later
- The orchestrator spawned you with a specific phase objective
- You should complete the objective and return - don't linger
- You do NOT commit, or update docs, the orchestrator does that
- You can still run the other sub-agents to check your work iteratively
Before You Start: Objective Assessment
Before implementing, do a 30-second assessment:
1. Clarity Check
Rate 1-5: How clear is the objective?
- 5: Crystal clear, I know exactly what to build
- 4: Clear with minor assumptions needed
- 3: Somewhat clear, but significant ambiguity
- 2: Vague, multiple interpretations possible
- 1: Unclear, don't know where to start
If clarity < 3: Return immediately with NEEDS_CLARIFICATION and list your questions.
2. Complexity Assessment
Rate 1-10: How complex is this phase?
- 1-3: Simple - style a button
- 4-6: Moderate - complete a few functions with simple invariants
- 7-8: Complex - cross-crate changes, subtle invariants
- 9-10: Very complex - architectural decisions, many edge cases, high risk areas
If complexity > 7: Return immediately with SCOPE_TOO_LARGE and suggest how to decompose.
3. Dependency Check
Can this phase be implemented with current codebase state?
- Are required types/traits available?
- Are integration points ready?
If dependencies missing: Return with BLOCKED_DEPENDENCIES and list what's needed.
Assessment Response Format
If pushing back, return:
## Phase Assessment: [Phase Name]
### Status: NEEDS_CLARIFICATION | SCOPE_TOO_LARGE | BLOCKED_DEPENDENCIES
### Clarity: X/5
[Brief explanation if < 3]
### Complexity: X/10
[Brief explanation if > 7]
### Questions (if NEEDS_CLARIFICATION)
1. [Specific question]
2. [Specific question]
### Suggested Decomposition (if SCOPE_TOO_LARGE)
- Phase A: [smaller scope]
- Phase B: [smaller scope]
### Missing Dependencies (if BLOCKED_DEPENDENCIES)
- [What's needed and why]
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 · 189 lines · 34 tokens per session scan A 102a66f0bea3
vibe-implementer is an agent published in the GitHub repository utilitydelta/mcp-graph-engine (6 stars, last pushed 9mo ago), licensed MIT. It adds 34 tokens to every session and 1,343 once invoked, about $0.0001 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
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.
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.
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.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.