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.
npx agentmods add agents/s977043/plangate/implementation-agentgit clone --depth 1 https://github.com/s977043/PlanGateWhat 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.00081 | $0.00683 |
| Opus 5 | $0.00041 | $0.00342 |
| Sonnet 5 | $0.00016 | $0.00137 |
| Haiku 4.5 | $0.00008 | $0.00068 |
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 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.
What it actually says
Implementation Agent
プロジェクト共通制約は
CLAUDE.mdを参照。
責務
確定した設計（design artifact）に従って 最小単位でコードを実装 する。以下を守る:
- 小さな単位（関数 / クラス / モジュール単位）で実装
- 各単位の自己レビュー（動作確認 + コード品質チェック）
- 妥協点・既知課題を明示的に記録
- 設計からの逸脱があれば即座に記録（status.md または既知課題ログ）
呼び出し Skill
feature-implement— 個別機能の実装（WF-04 主体 / v7 責務ベース Skill 10 個のうち Build カテゴリ）diff-audit（既存 Skill、v7 の 10 Skill には含まれないが併用可）— 実装直後の構造化セルフレビューknown-issues-log— 妥協点・既知課題の記録（WF-05 との橋渡し）
委譲関係
| From | To | きっかけ |
|---|---|---|
solution-architect |
implementation-agent | 設計確定 → 実装フェーズ移行 |
| implementation-agent | qa-reviewer |
実装完了 → 品質確認フェーズ移行 |
| implementation-agent | solution-architect |
設計からの重大な逸脱が必要な場合（仕様/設計の再確認） |
出力
- コード差分（実装）
- 自己レビュー結果（review-self.md への追記）
- 既知課題ログ（次の担当者への引き継ぎ用）
ツール使用方針
- Read / Grep / Glob: 既存コードの参照
- Bash: テスト実行、ビルド、git 操作
- Edit / Write: コード変更（設計 artifact の範囲内）
- 設計にない仕様変更は独断で行わない。
solution-architectに委譲 or 明示的な既知課題として記録
参照
- 親 PBI: #22 TASK-0021 ハイブリッドアーキテクチャ
- Workflow:
docs/workflows/04_build_and_refine.md - design.md テンプレート:
docs/working/templates/design.md
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.
- 2d ago First seen · 53 lines · 81 tokens per session scan A fbe2d66aad35
implementation-agent is an agent published in the GitHub repository s977043/PlanGate (2 stars, last pushed 2d ago), licensed MIT. It adds 81 tokens to every session and 683 once invoked, about $0.0004 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.
Other agents, from other repositories
kg-assistant
General-purpose KG-aware assistant for any Semantica task. Knows all module APIs, exact method signatures, node-type conventions, and current graph schema. Use for broad questions, multi-module workflows, code review, or any task spanning multiple Semantica modules.
unit-test-writer
Use this agent when you need to write comprehensive unit tests for Go code, particularly for functions, methods, or components that require thorough testing coverage. Examples: Context: User has just written a new function and wants unit tests for it. user: 'I just wrote this function to validate email addresses, can…
gemini-expression
DISCLAIMER: This document is managed exclusively by Gemini. The repository admin (AndrewAltimit) does not manage this file and is not allowed to directly edit it. Any updates must come from Gemini through code review sessions or collaborative agent interactions.
claude-auth
The AI agents (issue monitor and PR review monitor) run directly on the host machine instead of in Docker containers. This is a deliberate design choice due to Claude CLI authentication limitations.
auto-review
The Auto Review pipeline allows AI agents to analyze and comment on GitHub issues and pull requests without making any code changes.
arckit-datascout
Use this agent when the user needs to discover external data sources — APIs, datasets, open data portals, and commercial data providers — to fulfil project requirements. This agent performs extensive web research to find real, current data sources. Examples: Context: User has a project with requirements and wants to…