workflow

workflow is a skill for Claude Code, Codex from pitimon/8-habit-ai-dev. It costs 36 tokens per session (1,044 once invoked), scanned A, original, MIT.

A guided process for taking a software change from investigation through planning, coding, review, deployment, and monitoring.

In plain words
What is it for?
Use it when starting a feature or when you are unsure which development step should come next.
Why use it?
It prevents developers from jumping straight into code without deciding what to build, checking the result, or preparing to observe it after release.

Skill for Claude CodeCodex

Part of the 8-habit-ai-dev plugin — 24 skills, 2 agents, 1 hook shipped together

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/pitimon/8-habit-ai-dev/workflow
Any agent
npx skills add pitimon/8-habit-ai-dev --skill workflow
Clone the repo
git clone --depth 1 https://github.com/pitimon/8-habit-ai-dev

Made for: Claude Code, Codex.

Or install 8-habit-ai-dev, the plugin that ships this one along with the rest of its 24 skills, 2 agents, 1 hook.

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.

agentmods badge for workflow

README.md
[![agentmods](https://agentmods.dev/badge/skills/pitimon/8-habit-ai-dev/workflow.svg)](https://agentmods.dev/skills/pitimon/8-habit-ai-dev/workflow)
Your own site
<a href="https://agentmods.dev/skills/pitimon/8-habit-ai-dev/workflow"><img src="https://agentmods.dev/badge/skills/pitimon/8-habit-ai-dev/workflow.svg" alt="Measured on agentmods" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,044 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.00036 $0.01044
Opus 5 $0.00018 $0.00522
Sonnet 5 $0.00007 $0.00209
Haiku 4.5 $0.00004 $0.00104

Measured 4d ago against content hash 9bbf15b7b987, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 4d 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.

plugin/skills/workflow/SKILL.md · 81 lines

How it starts

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

7-Step Workflow Guide (เดินทีละก้าว)

All Habits | Anti-pattern: Jumping straight to code without planning, reviewing, or monitoring

Process

Walk the user through each step. For each step: explain what it does, ask whether to invoke or skip, and track progress.

The 7 Steps

Step Skill Purpose Skip if...
0 /research Investigate before specifying Requirements already clear, well-understood domain
1 /requirements Define what, why, who Single-line fix, formatting change
2 /design Architecture decisions Bug fix in existing pattern, no architecture impact
3 /breakdown Atomic tasks Single task, scope already clear
4 /build-brief Context before coding Familiar code, context still fresh
5 /review-ai Audit before commit Never skip
6 /deploy-guide Staging first No deployment involved
7 /monitor-setup Observability after deploy Monitoring already comprehensive

When the problem statement itself is fuzzy (before you know what to research), use superpowers:brainstorming from the claude-plugins-official:superpowers plugin — it ships a hard-gate collaborative design session with spec-doc-to-git. v2.4.1 removed our own /brainstorm skill in favor of that stronger equivalent (see ADR-006).

For Each Step

  1. Announce: "Step N: [skill] — [purpose]"
  2. Ask: "Invoke /[skill], skip (with reason), or stop here?"
  3. If invoke: Run the skill with the user's feature context
  4. If skip: Record the reason — honest skipping is fine, lazy skipping is not
  5. Move to next step

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

  1. 4d ago First seen · 81 lines · 36 tokens per session scan A 9bbf15b7b987

Subscribe to this mod's changes

workflow is a skill published in the GitHub repository pitimon/8-habit-ai-dev (3 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 1,044 once invoked, about $0.0002 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-31.

Related

Other skills, from other repositories

fix

Use to drive a bug fix from first report through close, with a "why didn't we catch it?" loop at the end. Triggers — "/engineer.fix", "a bug came in", "this is broken", "a user reported X", "there's a defect", "we have a regression", "this needs a fix", "another report", "more issues", "still failing", "validation…

swingerman/engineer · 100 tokens

next

Use at the start of a work session, or any time the question is "what should I pick up now" across the whole project. Triggers — "/engineer.next", "what's next", "what should I work on", "what should I do next", "where do I pick up".

swingerman/engineer · 64 tokens

crap-analyzer

Use to produce a risk-based refactor + test plan for recently-changed code on a diff/branch/PR by computing CRAP (complexity × untested) on changed methods. Multi-language — TypeScript, JavaScript, Python, Java, Kotlin, Go, Ruby, C#, Rust, PHP — auto-discovers how the repo generates coverage. Triggers …

swingerman/engineer · 109 tokens

post-merge

Use immediately after a PR is merged to clean up the local feature branch and resync main. Triggers — "/engineer.post-merge", "did we merge", "did we push", "PR merged", "post-merge cleanup", or right after a gh pr merge succeeds in the same session.

swingerman/engineer · 68 tokens

session-summary

Use at the end of a work session on a DAE feature, so the next session picks up cleanly. Triggers — "/engineer.session-summary", "wrap up the session", "write the session log", "I'm stopping for the day".

swingerman/engineer · 54 tokens

onboard

Use to bring a project into the DAE methodology, or to check an onboarded project for gaps. Triggers — "/engineer.onboard", "onboard this project", "set up DAE here", "adopt the methodology", or when a DAE skill fails because no manifest exists.

swingerman/engineer · 64 tokens