autocode

autocode is a command for Claude Code from charles001-wong/autocode-flow. It costs 38 tokens per session (1,833 once invoked), scanned A, original, MIT.

An automated development workflow that moves through planning, Test-Driven Development (writing tests before implementation), coding, testing, and verification. It accepts a feature description, a product requirements document, or a GitHub issue.

In plain words
What is it for?
Use it to develop a feature from a written request, requirements file, or GitHub issue, including test creation, implementation, full testing, linting, and review.
Why use it?
It coordinates the main development stages in order without stopping for manual handoffs between them. This keeps the planned work, tests, implementation, and checks connected.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Part of the autocode-flow plugin — 2 skills, 2 commands, 3 agents, 1 hook shipped together

Good fit Use it to develop a feature from a written request, requirements file, or GitHub issue, including test creation, implementation, full testing, linting, and review.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/charles001-wong/autocode-flow/autocode
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.

Clone the repo
git clone --depth 1 https://github.com/charles001-wong/autocode-flow

Made for: Claude Code.

Or install autocode-flow, the plugin that ships this one along with the rest of its 2 skills, 2 commands, 3 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 autocode

README.md
[![agentmods](https://agentmods.dev/badge/commands/charles001-wong/autocode-flow/autocode.svg)](https://agentmods.dev/commands/charles001-wong/autocode-flow/autocode)
Your own site
<a href="https://agentmods.dev/commands/charles001-wong/autocode-flow/autocode"><img src="https://agentmods.dev/badge/commands/charles001-wong/autocode-flow/autocode.svg" alt="Measured on agentmods" height="20"></a>
Per session 38 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,833 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00038 $0.01833
Opus 5 $0.00019 $0.00916
Sonnet 5 $0.00008 $0.00367
Haiku 4.5 $0.00004 $0.00183

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

Security

Grade A, and why

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

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.

commands/autocode.md · 234 lines

How it starts

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

/autocode-flow:autocode — Autonomous Development Pipeline

Execute the full development pipeline automatically: Plan → TDD → Code → Test → Verify.

No human intervention required. Just describe what you want or point to a PRD file.

Input

$ARGUMENTS — One of:

  • A feature description in natural language: /autocode-flow:autocode 新增用户登录注册功能
  • A PRD file reference: /autocode-flow:autocode prd @docs/user-auth-prd.md
  • A GitHub issue URL: /autocode-flow:autocode issue https://github.com/org/repo/issues/42

Orchestration Flow

Execute these phases sequentially and automatically. Do NOT stop to ask the user between phases. Each phase's output feeds directly into the next phase.

┌─────────────────────────────────────────────────────────────────────┐
│               /autocode-flow:autocode Pipeline                       │
│                                                                      │
│  ┌────────┐  ┌────────┐  ┌────────┐  ┌────────┐  ┌────────────┐   │
│  │  PLAN  │─►│  TDD   │─►│  CODE  │─►│  TEST  │─►│   VERIFY   │   │
│  │        │  │per step │  │per step│  │  full  │  │lint+review │   │
│  └────────┘  └────────┘  └────────┘  └────────┘  └────────────┘   │
│                                                                      │
│  Optional (if enabled):                                              │
│  ┌────────┐  ┌────────────┐                                         │
│  │  E2E   │─►│  SUMMARY   │                                        │
│  └────────┘  └────────────┘                                         │
└─────────────────────────────────────────────────────────────────────┘

Phase 1: PLAN (需求分析 & 任务拆解)

Goal: Convert the requirement into an ordered list of atomic implementation steps.

  1. If input is a PRD file, read and parse it.
  2. Search the codebase for related existing code, types, and patterns.
  3. Produce a structured plan:
{
  "feature": "User login and registration",
  "steps": [
    {
      "id": 1,
      "title": "Create user model and database schema",
      "files": ["internal/model/user.go", "internal/model/user_test.go"],
      "test_spec": "TestUserModel_Validate: valid/invalid email, password length",
      "depends_on": []
    },
    {
      "id": 2,
      "title": "Implement registration logic",
      "files": ["internal/logic/register_logic.go", "internal/logic/register_logic_test.go"],
      "test_spec": "TestRegisterLogic: success, duplicate email, weak password",
      "depends_on": [1]
    }
  ]
}

Read the full file on GitHub · 234 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. 6d ago First seen · 234 lines · 38 tokens per session scan A 2d9dca40686c

Subscribe to this mod's changes

autocode is a command published in the GitHub repository charles001-wong/autocode-flow (2 stars, last pushed 6mo ago), licensed MIT. It adds 38 tokens to every session and 1,833 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.