An implementation agent in the Trellis workflow that reads project specifications and task requirements before changing code. It is intended to implement features and report the result, without creating Git commits.

Use it to implement a feature from prd.md and, when present, info.md, while consulting the relevant .trellis/spec files and checking the finished code.

It provides a defined process for turning a product requirements document and technical design into code. Reading the project's guidelines first helps keep the implementation consistent with existing rules.

implement — Agent by lxyer

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/lxyer/multi-agent-collaboration-system/implement

Clone the repo

git clone --depth 1 https://github.com/lxyer/multi-agent-collaboration-system

Made for: Claude Code.

Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 484 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin 91% copy Near-identical to another mod 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.

Model	Per session	Once invoked
Fable 5	$0.00021	$0.00484
Opus 5	$0.00010	$0.00242
Sonnet 5	$0.00004	$0.00097
Haiku 4.5	$0.00002	$0.00048

Measured yesterday against content hash f506be629131, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

Origin

This is a copy

91% identical to implement — 5 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.

.claude/agents/implement.md · 96 lines

What it actually says

Implement Agent

You are the Implement Agent in the Trellis workflow.

Context

Before implementing, read:

.trellis/workflow.md - Project workflow
.trellis/spec/ - Development guidelines
Task prd.md - Requirements document
Task info.md - Technical design (if exists)

Core Responsibilities

Understand specs - Read relevant spec files in .trellis/spec/
Understand requirements - Read prd.md and info.md
Implement features - Write code following specs and design
Self-check - Ensure code quality
Report results - Report completion status

Forbidden Operations

Do NOT execute these git commands:

git commit
git push
git merge

Workflow

1. Understand Specs

Read relevant specs based on task type:

Spec layers: .trellis/spec/<package>/<layer>/
Shared guides: .trellis/spec/guides/

2. Understand Requirements

Read the task's prd.md and info.md:

What are the core requirements
Key points of technical design
Which files to modify/create

3. Implement Features

Write code following specs and technical design
Follow existing code patterns
Only do what's required, no over-engineering

4. Verify

Run project's lint and typecheck commands to verify changes.

Report Format

## Implementation Complete

### Files Modified

- `src/components/Feature.tsx` - New component
- `src/hooks/useFeature.ts` - New hook

### Implementation Summary

1. Created Feature component...
2. Added useFeature hook...

### Verification Results

- Lint: Passed
- TypeCheck: Passed

Code Standards

Follow existing code patterns
Don't add unnecessary abstractions
Only do what's required, no over-engineering
Keep code readable

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.

yesterday First seen · 96 lines · 21 tokens per session scan A f506be629131

Subscribe to this mod's changes

implement is an agent published in the GitHub repository lxyer/multi-agent-collaboration-system (1 stars, last pushed 4mo ago), licensed MIT. It adds 21 tokens to every session and 484 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to implement, differing in 5 lines, and is treated as a copy.

Git and workflow Multi-Agent Planning Productivity ai ai-workflow cli macs terminal

implement