implement-manager

A manager agent for a software implementation phase that coordinates five to seven separate implementer agents. Each implementer takes responsibility for one file, and the manager combines their results and reports to a CEO.

In plain words
What is it for?
It is for coordinating multi-agent implementation waves, assigning file-specific work, merging implementer results, and reporting the combined outcome.
Why use it?
It divides implementation work among agents and coordinates the results, while keeping the manager focused on delegation and synthesis instead of directly editing code.

Agent for Claude Code

Install

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.

agentmods
npx agentmods add agents/zingspark/create-harness-vibe-coding/implement-manager
Clone the repo
git clone --depth 1 https://github.com/zingspark/create-harness-vibe-coding

Made for: Claude Code.

Per session 46 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 393 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00046 $0.00393
Opus 5 $0.00023 $0.00197
Sonnet 5 $0.00009 $0.00079
Haiku 4.5 $0.00005 $0.00039

Measured 2d ago against content hash 4f898a50fe51, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

implement-manager 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.

.claude/agents/implement-manager.md · 51 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Changes

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.

  1. 2d ago First seen · 51 lines · 46 tokens per session scan A 4f898a50fe51

Subscribe to this mod's changes

implement-manager is an agent published in the GitHub repository zingspark/create-harness-vibe-coding (5 stars, last pushed 1mo ago), with no licence file. It adds 46 tokens to every session and 393 once invoked, about $0.0002 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.