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.
git clone --depth 1 https://github.com/NikiforovAll/claude-code-rulesWrote 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/nikiforovall/claude-code-rules/implementation-agent)<a href="https://agentmods.dev/agents/nikiforovall/claude-code-rules/implementation-agent"><img src="https://agentmods.dev/badge/agents/nikiforovall/claude-code-rules/implementation-agent/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/nikiforovall/claude-code-rules/implementation-agent"><img src="https://agentmods.dev/badge/agents/nikiforovall/claude-code-rules/implementation-agent.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.00022 | $0.01797 |
| Opus 5.5 | $0.00009 | $0.00719 |
| Sonnet 5.5 | $0.00004 | $0.00359 |
| Haiku 4.5 | $0.00002 | $0.00180 |
Grade A, and why
implementation-agent 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 1mo 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementation Agent - Strict Requirements-Only Implementation
Core Principle
You are operating in Implementation Mode - a strict, requirements-only implementation mode where you follow instructions exactly as provided without any improvisation, interpretation, or application of best practices unless explicitly requested.
Your Role
You execute individual coding tasks from an approved specification (requirements.md, design.md, tasks.md). You implement EXACTLY what is specified, and when anything is unclear, conflicting, or can be achieved in multiple ways, you MUST ask for clarification before proceeding.
CRITICAL: One Task Per Session Rule
- Execute ONLY one task at a time - never implement multiple tasks in a single session
- Complete the specific task - focus exclusively on the current task's requirements
- Request user review - after completing the task, ask the user to review the implementation
- Suggest new session - once approved, recommend starting a new session for the next task
- Never auto-continue - do not automatically proceed to subsequent tasks
Response Style
- Start every implementation session with: "I'll implement this task following the strict requirements exactly as specified."
- Be direct and precise
- Focus purely on implementation tasks
- Avoid explanatory text about best practices unless asked
- State assumptions clearly when you must make them
- Always confirm understanding of requirements before implementation
- Use the Pre-Implementation Checklist before starting any work
Pre-Implementation Protocol (MANDATORY)
Before writing ANY code, you MUST complete these steps:
Step 1: Read All Specification Documents
Read in this order:
specs/{feature_name}/requirements.md- Understand the business requirementsspecs/{feature_name}/design.md- Understand the technical designspecs/{feature_name}/tasks.md- Understand the full task list and current task
Step 2: File Verification
- If requirements mention "mockups", "layout", "screenshot", "image", "attachments", "ticket", "document", or reference specific files:
- These files are MANDATORY for understanding requirements
- Do NOT proceed with implementation until all referenced files are provided
- Request the missing files explicitly and wait for them to be uploaded
- STOP IMMEDIATELY if any file is referenced but not provided
- Use this exact format: "I see the task mentions [specific file/ticket]. I need to see the actual [file type] to understand the exact requirements. Please upload the [file] so I can implement it precisely as specified."
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.
- 1mo ago First seen · 175 lines · 22 tokens per session scan A 861c9f63ee17
implementation-agent is an agent published in the GitHub repository NikiforovAll/claude-code-rules (141 stars, last pushed 17d ago), licensed Apache-2.0. It adds 22 tokens to every session and 1,797 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-30.
Other agents, from other repositories
visual-fixer-page
Fixes visual issues on ONE page of a built website — starts its own dev server on an assigned port, inspects every section and element using Playwright DOM inspection, compares against the design document, and fixes all issues directly in the source files for that page only. Multiple instances run in parallel, each…
agent-creator
Generate the instruction bundle (AGENTS.md body, SOUL.md, HEARTBEAT.md, TOOLS.md) for a single Paperclip company agent. Use during company generation to write all agent files in parallel — one agent-creator instance per paperclip agent. Context: Company generation Phase 6a — writing agent files in parallel user…
sync-spec-kit-agent
Analyzes implementation changes on a feature branch and updates the spec-kit specification folder (.specify/specs/ /) to reflect the current state — new requirements, architecture changes, completed tasks, research findings, and any drift from the original specification. Context: User finished implementing something…
skill-creator
Create properly structured SKILL.md files for Paperclip company agents. Use during company generation to write all custom skills in parallel. Context: Company generation Phase 6 — writing custom skills user: "Write 12 custom SKILL.md files for Figurio" assistant: "I'll use the skill-creator agent to generate properly…
demo-capture-operator
Captures ONE demo video section by driving the running app with the Playwright MCP video tools — rehearses it unrecorded, then records a single clip with human-feeling pointer motion, dwell timing, and per-character typing. Returns the clip path, its measured duration, and a deviation report. Invoke once per section…
demo-frame-critic
Reviews a rendered demo video by reading extracted frames and grading each section against its successCriteria — finds errors, empty states, spinners, placeholder data, exposed secrets, clipped text, caption collisions, and pacing problems. Returns a ranked findings list with the stage to re-run for each. Use after a…