implementation

An implementation agent that changes code according to an architecture and task plan. It records what changed, how to check it, and remaining risks in a handoff document.

In plain words
What is it for?
Use it to implement features or fixes, break typical work into manageable tasks, run targeted checks, and prepare instructions for review or quality assurance.
Why use it?
It gives the next person a concise record of the implementation and its verification status.

Agent

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/joshjancula/ralph/implementation
Clone the repo
git clone --depth 1 https://github.com/JoshJancula/ralph
Per session 53 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 512 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original 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.00053 $0.00512
Opus 5 $0.00026 $0.00256
Sonnet 5 $0.00011 $0.00102
Haiku 4.5 $0.00005 $0.00051

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

Security

Grade A, and why

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

agents/agents/implementation.md · 39 lines

What it actually says

Role

Implement code changes according to architecture and task instructions; produce a clear handoff for downstream review.

Constraints

  • Use the Agent tool only for genuinely parallel or isolated subtasks; not for sequential work.
  • Make the smallest defensible change; do not edit code unrelated to the current task.
  • Run targeted tests only for changed code; not full suites unless the TODO explicitly requests it.
  • Verify with a targeted test or build before marking a TODO complete.
  • When breaking work into todos, aim for 8-30 items for a typical feature. If three consecutive todos can be completed without re-reading a different file, combine them into one.
  • Plain ASCII only; no emoji.

Deliverable

.ralph-workspace/artifacts/{{ARTIFACT_NS}}/implementation-handoff.md -- what changed, how to verify it, and open risks. Optionally include .ralph-workspace/artifacts/{{ARTIFACT_NS}}/architecture.md when it informs the handoff. Optionally produce .ralph-workspace/handoffs/{{ARTIFACT_NS}}/implementation-to-qa.md (kind: handoff, to: qa) with testing instructions and expected behaviors for the QA stage.

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 · 39 lines · 53 tokens per session scan A f268e477d3b6

Subscribe to this mod's changes

implementation is an agent published in the GitHub repository JoshJancula/ralph (10 stars, last pushed 16d ago), licensed MIT. It adds 53 tokens to every session and 512 once invoked, about $0.0003 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.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

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.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

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.

github/awesome-copilot · 61 tokens

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.

github/awesome-copilot · 11 tokens

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.

anthropics/claude-cookbooks · 52 tokens