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/ANcpLua/ancplua-claude-pluginsWrote 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/commands/ancplua/ancplua-claude-plugins/batch-implement)<a href="https://agentmods.dev/commands/ancplua/ancplua-claude-plugins/batch-implement"><img src="https://agentmods.dev/badge/commands/ancplua/ancplua-claude-plugins/batch-implement/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/commands/ancplua/ancplua-claude-plugins/batch-implement"><img src="https://agentmods.dev/badge/commands/ancplua/ancplua-claude-plugins/batch-implement.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.00035 | $0.01177 |
| Opus 5.5 | $0.00014 | $0.00471 |
| Sonnet 5.5 | $0.00007 | $0.00235 |
| Haiku 4.5 | $0.00003 | $0.00118 |
Grade A, and why
batch-implement 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 14d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BATCH IMPLEMENT — Parallel Items with Shared Pattern
Extract pattern. Parallelize. Review consistency. Verify.
Type: $0 (diagnostics|tests|endpoints|features|fixes|migrations) Items: $1 (comma-separated list)
TEAM ARCHITECTURE
BATCH LEAD (You — Orchestrator)
│
├─ Phase 1: PATTERN EXTRACTION (1 agent)
│ └── template-extractor
│ └── → template ready
│
├─ Phase 2: PARALLEL IMPLEMENTATION (1 agent per item)
│ ├── implementer-item-1 ... implementer-item-N
│ └── GATE → all complete
│
├─ Phase 3: CONSISTENCY REVIEW (1 agent)
│ └── consistency-reviewer
│ └── → fix issues found
│
└─ Phase 4: VERIFICATION (direct)
└── Build + Test + Lint → DONE | BLOCKED
<CRITICAL_EXECUTION_REQUIREMENT>
STEP -1 — Inherit Prior Findings:
If <EXODIA_FINDINGS_CONTEXT> tag exists in session context, read .eight-gates/artifacts/findings.json.
Filter findings matching items in $0. Inject matching findings into Phase 2 agent prompts as context.
RUN ALL 4 PHASES WITHOUT STOPPING.
- Launch 1 template extractor
- Launch 1 implementer PER ITEM in ONE message (parallel)
- Launch 1 consistency reviewer
- Run verification directly
Use TodoWrite: one todo per item, mark complete as each finishes.
YOUR NEXT MESSAGE: 1 Task tool call for Phase 1. NOTHING ELSE.
</CRITICAL_EXECUTION_REQUIREMENT>
PHASE 1: PATTERN EXTRACTION — 1 Agent
template-extractor
subagent: feature-dev:code-explorer You are template-extractor. Extract the implementation pattern. TYPE: $0 | ITEMS: $1 Find: existing implementations of this type, common structure, required boilerplate, test patterns, registration/wiring. Create template: file structure, code skeleton, naming conventions, integration points. Output: Implementation template with placeholders
PHASE 2: PARALLEL IMPLEMENTATION
Parse $1 (comma-separated). Launch ONE agent PER ITEM in ONE message.
implementer-item-N (one per item)
subagent: feature-dev:code-architect IMPLEMENT: [ITEM_NAME from $1] | TYPE: $0 Using template from Phase 1. Follow TDD:
- Write failing test → 2. Implement → 3. Verify pass
Checklist: follows pattern, unit test, implementation, no copy-paste errors.
FILE OWNERSHIP: You own ONLY files for YOUR item. List owned files at the top of your output. DO NOT modify shared files (DI registrations, route tables, module exports, index files, barrel files). Leave a
// TODO: register [ITEM_NAME]comment in your output — the consistency-reviewer handles all wiring. Output: Files created with paths + OWNED FILES list
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.
- 14d ago First seen · 154 lines · 35 tokens per session scan A c6f6376c8973
batch-implement is a command published in the GitHub repository ANcpLua/ancplua-claude-plugins (6 stars, last pushed 3d ago), licensed MIT. It adds 35 tokens to every session and 1,177 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-10-01.
Other commands, from other repositories
checkpoint
Save verification state and progress checkpoint.
verify-work
Verify feature, bug, UI, API, mobile, security, or deployment work against acceptance criteria.
workflow-implement
Exécuter la phase d'Implémentation - développement sprint avec TDD/BDD.
aqa-flow
Router workflow for test automation: routes to ui-aqa-flow, api-aqa-flow, or testgen-flow. Kept for backward compatibility.
complete
Review implementation evidence and plan the spec completion transaction.
sddp-implement-qc-loop
Command description: Run implement and QC in a continuous loop. Argument hint: [optional: feature directory or branch name] Command category: orchestration Prerequisites: spec, plan, tasks.