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/ww-w-ai/bkit-claude-code/pdca-iteratorgit clone --depth 1 https://github.com/ww-w-ai/bkit-claude-codeWhat 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.00088 | $0.02950 |
| Opus 5 | $0.00044 | $0.01475 |
| Sonnet 5 | $0.00018 | $0.00590 |
| Haiku 4.5 | $0.00009 | $0.00295 |
Grade A, and why
pdca-iterator 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.
How it starts
The opening of the file, as written. The whole thing — 421 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When NOT to use this agent
Do NOT use for: initial development, research tasks, design document creation, or when user explicitly wants manual control.
Delegation notes
Also invoked by sprint-orchestrator during the Sprint iterate phase (v2.1.13) to drive iterateHistory until matchRate >= 90 or the ITERATION_EXHAUSTED auto-pause trigger fires. Iteration rules (v1.3.0): maximum 5 iterations per session; re-run gap-detector after each fix cycle; stop when Match Rate >= 90% or max iterations reached; report to report-generator when complete (see Auto-Invoke Conditions and Iteration Control below).
PDCA Iterator Agent
Role
Implements the Evaluator-Optimizer pattern from Anthropic's agent architecture. Automatically iterates through evaluation and improvement cycles until quality criteria are met.
Core Loop
flowchart TB
subgraph Loop["Evaluator-Optimizer Loop"]
direction TB
Gen["Generator<br/>LLM"]
Output["Output"]
Eval["Evaluator<br/>LLM"]
Decision{Pass Criteria?}
Complete["Complete"]
Gen -->|"Generate"| Output
Output --> Eval
Eval --> Decision
Decision -->|"Yes"| Complete
Decision -->|"No"| Gen
Eval -.->|"Improvement<br/>Suggestions"| Gen
Output -.->|"Feedback"| Gen
end
style Gen fill:#4a90d9,color:#fff
style Eval fill:#d94a4a,color:#fff
style Output fill:#50c878,color:#fff
style Decision fill:#f5a623,color:#fff
style Complete fill:#9b59b6,color:#fff
Evaluator Types
1. Design-Implementation Evaluator
Uses gap-detector agent to evaluate implementation against design.
Evaluation Criteria:
- API endpoint match rate >= 90%
- Data model field match rate >= 90%
- Component structure match >= 85%
- Error handling coverage >= 80%
2. Code Quality Evaluator
Uses code-analyzer agent to evaluate code quality.
Evaluation Criteria:
- No critical security issues
- Complexity per function <= 15
- No duplicate code blocks (> 10 lines)
- Test coverage >= 80% (if tests exist)
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 · 421 lines · 88 tokens per session scan A ddb2d6fe69f1
pdca-iterator is an agent published in the GitHub repository ww-w-ai/bkit-claude-code (594 stars, last pushed 16d ago), licensed Apache-2.0. It adds 88 tokens to every session and 2,950 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-30.
Other agents, from other repositories
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
model-compatibility
Recommendation matrix for which model to pair with each OMC/OMO agent, framed around cost vs. quality. This page exists so the recurring "어떤 모델을 어느 agent에 박아야 함?" question stops being tribal Discord knowledge.
kimi
Kimi CLI is Moonshot's coding agent. In CCR it is CLI only and always uses Only opened from CCR.
dynamic-agents
Dynamic agents use functions instead of static values for instructions, model, and tools. These functions receive runtime context and return the appropriate configuration for each operation.
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
context-manager
Use this agent when you need to manage context across multiple agents and long-running tasks, especially for projects exceeding 10k tokens. This agent is essential for coordinating complex multi-agent workflows, preserving context across sessions, and ensuring coherent state management throughout extended development…