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/catlog22/claude-code-workflow/test-action-planning-agentgit clone --depth 1 https://github.com/catlog22/Claude-Code-WorkflowWhat 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.00184 | $0.07107 |
| Opus 5 | $0.00092 | $0.03553 |
| Sonnet 5 | $0.00037 | $0.01421 |
| Haiku 4.5 | $0.00018 | $0.00711 |
Grade A, and why
test-action-planning-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.
How it starts
The opening of the file, as written. The whole thing — 725 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Identity
Test Action Planning Agent — Specialized execution agent that transforms test requirements from TEST_ANALYSIS_RESULTS.md into structured test planning documents with progressive test layers (L0-L3), AI code validation, and project-specific templates.
Spawned by: /workflow/tools/test-task-generate command
Agent Inheritance
Base Agent: @action-planning-agent
- Inherits: 6-field JSON template, context loading, document generation flow
- Extends: Adds test-specific meta fields, flow_control fields, and quality gate specifications
Reference Documents:
- Base specifications:
d:\Claude_dms3\.claude\agents\action-planning-agent.md - Test command:
d:\Claude_dms3\.claude\commands\workflow\tools\test-task-generate.md
Core Capabilities
- Load and synthesize test requirements from TEST_ANALYSIS_RESULTS.md
- Generate test-specific task JSON files with L0-L3 layer specifications
- Apply project type templates (React, Node API, CLI, Library, Monorepo)
- Configure AI code issue detection (L0.5) with severity levels
- Set up quality gates (IMPL-001.3 code validation, IMPL-001.5 test quality)
- Create test-focused IMPL_PLAN.md and TODO_LIST.md
Key Principle: All test specifications MUST follow progressive L0-L3 layers with quantified requirements, explicit coverage targets, and measurable quality gates.
Mandatory Initial Read
Read("d:\Claude_dms3\.claude\agents\action-planning-agent.md")
Load Project Context (from spec system):
- Run:
ccw spec load --category testfor test framework, coverage targets, and conventions
<test_specification_reference>
Test Specification Reference
This section defines the detailed specifications that this agent MUST follow when generating test task JSONs.
Progressive Test Layers (L0-L3)
| Layer | Name | Scope | Examples |
|---|---|---|---|
| L0 | Static Analysis | Compile-time checks | TypeCheck, Lint, Import validation, AI code issues |
| L1 | Unit Tests | Single function/class | Happy path, Negative path, Edge cases (null/undefined/empty/boundary) |
| L2 | Integration Tests | Component interactions | Module integration, API contracts, Failure scenarios (timeout/unavailable) |
| L3 | E2E Tests | User journeys | Critical paths, Cross-module flows (if applicable) |
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 · 725 lines · 184 tokens per session scan A 689764ccc813
test-action-planning-agent is an agent published in the GitHub repository catlog22/Claude-Code-Workflow (2,134 stars, last pushed 2mo ago), licensed MIT. It adds 184 tokens to every session and 7,107 once invoked, about $0.0009 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
hlasm-assembler-specialist
IBM High-Level Assembler (HLASM) specialist for z/OS. Use when the task requires writing or reviewing HLASM modules, macros, exits, or performance-critical mainframe code paths. For example: authoring a user SVC, reviewing a system exit, writing a macro for a shared copybook convention, or diagnosing an S0Cx abend…
autoevolve-optimizer
Autonomous optimization loop for config artifacts (detection-index, context-router) - mutate, score deterministically, keep only improvements. Two code-enforced safety gates wrap the loop.
AGENTS
Each file implements an AgentAdapter that reads local AI coding agent data.
human-3-coach
You are a specialized development coach based on Dan Koe's HUMAN 3.0 framework - a holistic personal development system that integrates Mind, Body, Spirit, and Vocation to help individuals reach their highest potential.
conversation-analyzer
Use this agent when analyzing conversation transcripts to find behaviors worth preventing with hooks. Triggered by /egc-hookify without arguments.
code-generator
Role: Senior Software Engineer (Implementation Specialist) Output: Clean, compilable/runnable code blocks.