What is agentic-workflow?

A staged workflow for handling implementation tasks with separate agents for research, planning, implementation, and validation.

Organizing multi-step coding work, researching an approach, producing an implementation plan, and validating the finished changes.

It keeps the main conversation small and creates written outputs between stages, making complex changes easier to coordinate and review.

agentic-workflow — Skill for Claude Code by parcadei: A staged workflow for handling implementation tasks with separate…

About the project

Continuous-Claude-v3 is a Claude Code development environment that preserves working context between sessions, coordinates specialized agents, and stores project knowledge through ledgers, handoffs, and analysis tools. It is for people using Claude Code on ongoing or complex software work. Its catalogue entries are the skills, agents, hooks, plugin, and setting that provide its workflows and orchestration.

parcadei/Continuous-Claude-v3 · 3,936 stars · on GitHub

Install

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.

agentmods

npx agentmods add skills/parcadei/continuous-claude-v3/agentic-workflow

Any agent

npx skills add parcadei/Continuous-Claude-v3 --skill agentic-workflow

Clone the repo

git clone --depth 1 https://github.com/parcadei/Continuous-Claude-v3

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/parcadei/continuous-claude-v3/agentic-workflow.svg)](https://agentmods.dev/skills/parcadei/continuous-claude-v3/agentic-workflow)

Your own site

<a href="https://agentmods.dev/skills/parcadei/continuous-claude-v3/agentic-workflow"><img src="https://agentmods.dev/badge/skills/parcadei/continuous-claude-v3/agentic-workflow.svg" alt="Measured on agentmods" height="20"></a>

Per session 9 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 985 The whole file, excluding the scripts and references it only reads on demand.

Security scan B 1 finding. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00009	$0.00985
Opus 5	$0.00005	$0.00492
Sonnet 5	$0.00002	$0.00197
Haiku 4.5	$0.00001	$0.00098

Measured 6d ago against content hash 3f4e0204d9ba, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade B, and why

agentic-workflow scanned grade B with 1 finding 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 6d 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

find .claude/cache/agents -name "*.md" -mmin -5

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

agentic-workflow — 100% identical, 266 lines differ

.claude/skills/agentic-workflow/SKILL.md · 134 lines

How it starts

The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agentic Workflow Pattern

Standard multi-agent pipeline for implementation tasks.

Architecture Principles

Use run_in_background: true for all agents to keep main context minimal
Use Task tool (never TaskOutput) to avoid receiving full agent transcripts
Agents write outputs to .claude/cache/agents/<stage>/ for injection into subsequent agents
Main conversation is pure orchestration — no heavy lifting, only coordination

Workflow Stages

1. Research Agent

Task(subagent_type="oracle", run_in_background=true, prompt="""
Query NIA Oracle (via /nia-docs skill) to verify approach and gather best practices.

Output to: .claude/cache/agents/oracle/<task>-research.md
""")

Enforce NIA as the research layer
Output: Research findings

2. Planning Agent

Task(subagent_type="plan-agent", run_in_background=true, prompt="""
Read: .claude/cache/agents/oracle/<task>-research.md
Use RP-CLI to analyze the target codebase section.
Generate implementation plan informed by research.

Output to: .claude/cache/agents/plan-agent/<task>-plan.md
""")

Receives: Research agent output as context
Output: Implementation plan

3. Validation Agent

Task(subagent_type="validate-agent", run_in_background=true, prompt="""
Read: .claude/cache/agents/plan-agent/<task>-plan.md
Read: .claude/cache/agents/oracle/<task>-research.md
Review plan against research findings and best practices.

Output to: .claude/cache/agents/validate-agent/<task>-validated.md
""")

Reviews plan against research
Output: Validated plan with amendments

4. Implementation Agent

Task(subagent_type="agentica-agent", run_in_background=true, prompt="""
Read: .claude/cache/agents/validate-agent/<task>-validated.md
Read: .claude/cache/agents/oracle/<task>-research.md

TDD approach: Write failing tests FIRST, then implement.
Run tests to verify.

Output summary to: .claude/cache/agents/implement-agent/<task>-implementation.md
""")

Receives: Validated plan + research context
TDD: Failing tests first
Output: Implementation + tests

Read the full file on GitHub · 134 lines

Changes

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.

6d ago First seen · 134 lines · 9 tokens per session scan B 3f4e0204d9ba

Subscribe to this mod's changes

agentic-workflow is a skill published in the GitHub repository parcadei/Continuous-Claude-v3 (3,936 stars, last pushed 7mo ago), licensed MIT. It adds 9 tokens to every session and 985 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Building agents Planning agents claude-code claude-code-cli claude-code-hooks claude-code-mcp claude-code-skills

fizzy-workflow

Use for guided Fizzy.do workflows: "set up Fizzy", "configure Fizzy for this project", "sync my work to Fizzy", "review my Fizzy progress", "end of session cleanup". Provides step-by-step guidance for common operations.

keskinonur/claude-plugin-fizzy · 57 tokens

tdd

Use when implementing features or bug fixes test-first.

Kripu77/software-factory · 13 tokens

nil

The inverse of /sfl. Where sfl saved each window for later, /nil says later is now: it reopens them. You choose which to bring back.

wasulajr/headsup · 153 tokens

e2e-test-skill

E2E test skill for validation.

alex-feel/claude-code-toolbox · 14 tokens

headsup-config

Unified settings hub for headsup (Claude Code's iTerm2 status hooks). One command with a section as the first word, then that section's args. Sections: newtabs (New Claude Tab / Cmd-Opt-C launch mode), colors (idle/processing/waiting tab colors), label (this tab's title + badge), notify (the 'Claude is waiting' macOS…