code-dev-workflow

A coding workflow that divides work into Explore, Read, and Author phases, using outlines and selected line ranges to manage context.

In plain words
What is it for?
Use it to inspect a codebase, summarize relevant sections, and make focused changes in stages.
Why use it?
It helps prevent large files from overwhelming the session and keeps coding changes organized.

Skill for Claude CodeCodex

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/demondamon/agenticx/code-dev-workflow
Any agent
npx skills add DemonDamon/AgenticX --skill code-dev-workflow
Clone the repo
git clone --depth 1 https://github.com/DemonDamon/AgenticX

Made for: Claude Code, Codex.

Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 217 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.

ModelPer sessionOnce invoked
Fable 5 $0.00022 $0.00217
Opus 5 $0.00011 $0.00109
Sonnet 5 $0.00004 $0.00043
Haiku 4.5 $0.00002 $0.00022

Measured yesterday against content hash 67e40186b979, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

code-dev-workflow 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 yesterday.

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

agenticx/skills/bundled/code-dev-workflow/SKILL.md · 26 lines

What it actually says

Code Dev Workflow

Use when the session is in code_dev mode.

Phases

  1. Explorecode_outline, grep, lsp_*, code_search (if enabled). Write scratchpad_write(key="phase", value="explore") and a file list to read.
  2. Readfile_read with start_line/end_line only. Summarize into scratchpad. Then phase=read.
  3. Authorfile_write skeleton first, then section-by-section updates. phase=author.

Rules

  • Never read entire large files without outline + line ranges.
  • Do not mirror document milestones into todo_write unless executing multi-step work.
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.

  1. yesterday First seen · 26 lines · 22 tokens per session scan A 67e40186b979

Subscribe to this mod's changes

code-dev-workflow is a skill published in the GitHub repository DemonDamon/AgenticX (219 stars, last pushed yesterday), licensed Apache-2.0. It adds 22 tokens to every session and 217 once invoked, about $0.0001 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.