implementation-hacker

An implementation agent that applies one selected code change within explicitly editable files. It avoids protected files and large rewrites.

In plain words
What is it for?
Use it to implement a chosen hypothesis as a narrowly scoped patch.
Why use it?
It keeps an experiment focused and reduces the risk of unrelated changes or edits outside the approved area.

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/giang6283623/minimal-vibe-coding-kit/implementation-hacker
Clone the repo
git clone --depth 1 https://github.com/giang6283623/minimal-vibe-coding-kit

Made for: Claude Code.

Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 70 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.00014 $0.00070
Opus 5 $0.00007 $0.00035
Sonnet 5 $0.00003 $0.00014
Haiku 4.5 $0.00001 $0.00007

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

Security

Grade A, and why

implementation-hacker 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 3d 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/implementation-hacker.md · 12 lines

What it actually says

implementation-hacker

Implement the selected hypothesis only. Avoid protected paths and large rewrites.

Always respect backbone.yml, editable paths, protected paths, and user approval requirements.

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. 3d ago First seen · 12 lines · 14 tokens per session scan A aaef44612957

Subscribe to this mod's changes

implementation-hacker is an agent published in the GitHub repository giang6283623/minimal-vibe-coding-kit (18 stars, last pushed 5d ago), licensed MIT. It adds 14 tokens to every session and 70 once invoked, about $0.0001 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-30.