A coding workflow that carries out a project plan one task at a time, checking each task before marking it done. TDD means writing a failing test, making it pass, and then improving the code.

Use it to execute PLAN.md files, read required project context, apply changes, verify acceptance conditions, update task status, and create small commits.

It keeps implementation aligned with the written plan and makes progress, scope changes, and differences from the plan visible.

dev-coding — Skill for Claude Code and Codex by calneymgp/solodev

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.

Any agent

npx skills add calneymgp/solodev --skill dev-coding

Clone the repo

git clone --depth 1 https://github.com/calneymgp/solodev

Made for: Claude Code, Codex.

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/calneymgp/solodev/dev-coding/github.svg)](https://agentmods.dev/skills/calneymgp/solodev/dev-coding)

Your own site

<a href="https://agentmods.dev/skills/calneymgp/solodev/dev-coding"><img src="https://agentmods.dev/badge/skills/calneymgp/solodev/dev-coding/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/calneymgp/solodev/dev-coding"><img src="https://agentmods.dev/badge/skills/calneymgp/solodev/dev-coding.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

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

Security scan C 2 findings. A grade says what 26 rules found in the file — not that it is safe.

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.00135	$0.02072
Opus 5.5	$0.00054	$0.00829
Sonnet 5.5	$0.00027	$0.00414
Haiku 4.5	$0.00014	$0.00207

Measured 1mo ago against content hash e881f7a1507b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

dev-coding scanned grade C with 2 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 1mo 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

- Vai rodar comando destrutivo (force push, drop table, rm -rf)

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

4. Cheque cada `acceptance` — grep / curl / output esperado

skills/dev-coding/SKILL.md · 159 lines

How it starts

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

/dev-coding — Executar PLAN.md task por task

Esta skill assume que existe .plans/<feature>/PLAN.md produzido por /dev-plan (ou compatível). Executa uma task por vez, com verificação dura no fim de cada uma.

Pré-condições

Existe <workspace>/.plans/<feature>/PLAN.md (ou usuário aponta o path)
Você pode escrever e executar comandos no projeto

Se não houver PLAN.md, pare e sugira /dev-plan antes. Se for bug isolado sem plano, sugira /dev-fix.

Ritual de início de sessão

Na primeira execução da sessão (e após cada reset de contexto):

PLAN: <feature> — [████████░░░░] 4/9 tasks ✅
Próxima: task-05 (<tipo>, effort <S/M/L>) — <título>

1 mensagem, depois execute. O usuário sempre sabe onde está sem perguntar.

Processo por task

1. Carregue o contexto mínimo

Read .plans/<feature>/PLAN.md integralmente
Read CLAUDE.md do projeto + sub-CLAUDEs citados em ## Affected Areas
Identifique a próxima task com status: [ ] cuja dependência (depends_on) já está [x]
Read todos os read_first da task escolhida ANTES de qualquer edit

2. Despache pelo tipo

`type: auto` (execução direta)

Anuncie em 1 frase: "task-XX: <título> — vou tocar ."
Execute as subtasks da action em ordem
Rode o must_pass (typecheck, build, test, lint conforme aplicável)
Cheque cada acceptance — grep / curl / output esperado
Marque [x] em cada acceptance no PLAN.md
Atualize ## Status Log com timestamp + identificador (commit hash se for committar)
Reporte ao usuário em 2-3 linhas: o que mudou, o que verificou, próxima task

`type: tdd` (red-green-refactor vertical)

Princípio: tracer bullets, NÃO horizontal slicing. UM teste → UMA implementação → REPETE. Nunca escrever todos os testes primeiro.

Por subtask:

RED:   escreva 1 teste para 1 behavior — rode → vê falhar
GREEN: código mínimo para passar — rode → vê passar
       (não antecipe próximos testes; não adicione features especulativas)
[Após todas as subtasks GREEN: REFACTOR — só quando GREEN, nunca quando RED]

Read the full file on GitHub · 159 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.

1mo ago First seen · 159 lines · 135 tokens per session scan C e881f7a1507b

Subscribe to this mod's changes

dev-coding is a skill published in the GitHub repository calneymgp/solodev (2 stars, last pushed 1mo ago), licensed MIT. It adds 135 tokens to every session and 2,072 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Claude Code Commits Git and workflow Planning ai-coding-assistant anthropic claude-skills dev-workflow prompt-engineering

github-workflow

GitHub best practices for pull requests, code reviews, issues, Actions workflows, and repository management.

Mindrally/skills · 23 tokens

git-workflow

Git conventions and workflow guidelines using Conventional Commits, branching strategies, and best practices for version control.

Mindrally/skills · 23 tokens

lerna

Best practices for Lerna monorepo management, versioning, and publishing.

Mindrally/skills · 18 tokens

git-pushing

Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activates when user says "push changes", "commit and push", "push this", "push to github", or similar git workflow requests.

mhattingpete/claude-skills-marketplace · 70 tokens

github-activity

Report what happened across GitHub repositories over a time window, read only. Invoke when the user asks what merged, which issues were opened or closed, or what moved between milestones since a date or since the last report, across one or more repositories.

curie-eng/curie · 54 tokens

implement-issue

Turn one labelled GitHub issue into one reviewed pull request, or stop with a stated reason. Use for every factory run; the message is a link to the issue.

curie-eng/curie · 38 tokens

dev-coding