Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add charles001-wong/autocode-flow/plugin install autocode-flowWrote 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.
[](https://agentmods.dev/commands/charles001-wong/autocode-flow/autocode-new)<a href="https://agentmods.dev/commands/charles001-wong/autocode-flow/autocode-new"><img src="https://agentmods.dev/badge/commands/charles001-wong/autocode-flow/autocode-new/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.
<a href="https://agentmods.dev/commands/charles001-wong/autocode-flow/autocode-new"><img src="https://agentmods.dev/badge/commands/charles001-wong/autocode-flow/autocode-new.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00025 | $0.00558 |
| Opus 5 | $0.00013 | $0.00279 |
| Sonnet 5 | $0.00005 | $0.00112 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
autocode-new 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/autocode-flow:autocode-new — Generate Project-Specific Dev Pipeline
This command bootstraps a complete autocode development pipeline for the current project
through a 3-phase workflow: Scan → Interview → Generate.
Execution Flow
Step 1: Scan the Project
Run the scanner to detect the project's tech stack:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/scan-project.sh" "$(pwd)"
Parse the JSON output and present a summary to the user:
📋 Project Scan Results
━━━━━━━━━━━━━━━━━━━━━━
Project: {project_name}
Language: {language}
Framework: {framework}
Pkg Mgr: {package_manager}
Tests: {test_framework}
Linter: {linter}
CI/CD: {ci_cd}
Docker: {has_docker}
Ask: "Does this look correct? Any corrections before we proceed?"
Step 2: Interview — Collect Pipeline Preferences
Walk through each stage one at a time. Use the collected scan data to provide smart defaults. For each stage, present the question, wait for an answer, confirm, then move to the next.
Stage order: Plan → TDD → Code → Test → E2E → CI/CD
Read the autocode-interviewer agent at ${CLAUDE_PLUGIN_ROOT}/agents/autocode-interviewer.md
for the detailed question set per stage.
Step 3: Generate the autocode System
Read the autocode-generator agent at ${CLAUDE_PLUGIN_ROOT}/agents/autocode-generator.md
and follow its workflow.
For each file to generate:
- Read the corresponding template from
${CLAUDE_PLUGIN_ROOT}/templates/ - Replace
{{variables}}with project-specific values - Remove conditional sections that don't apply
- Write the file to the correct path in the user's project
- If the file already exists, ask user: overwrite / merge / skip
Step 4: Summary
After generation, display:
- List of all created files
- Available commands:
/plan,/tdd,/code,/test,/e2e,/deploy - Suggest: "Try
/plan <your next feature>to test the pipeline!"
Important
- ALWAYS present scan results before interviewing
- ALWAYS ask ONE stage at a time during the interview
- ALWAYS confirm the full config before generating
- NEVER overwrite existing files without asking
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.
- 9d ago First seen · 73 lines · 25 tokens per session scan A 0afc4f615be6
autocode-new is a command published in the GitHub repository charles001-wong/autocode-flow (2 stars, last pushed 6mo ago), licensed MIT. It adds 25 tokens to every session and 558 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-31.
Other commands, from other repositories
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
help
Explain Ralph Wiggum technique and available commands.
update-counts
Update all hardcoded counts (skills, agents, marketplace repos/skills) across documentation from filesystem.
app-architect
Architect a new app or service — plain-language chat, living plan artifacts.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
pr-description
Generate a PR title and description from the current branch diff against main.