A complete workflow command for aitm, a command-line tool that coordinates AI coding agents to develop changes in one checkout and merge them through GitHub.

Use it to investigate bugs, reproduce issues, split feature work among parallel agents, implement and verify changes, open and merge pull requests, and release to npm only when explicitly requested.

It turns the work from understanding a request through testing and merging into one tracked process, with checks under both Bun and Node.

How developerz-ai/ai-task-master configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to developerz-ai/ai-task-master. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/developerz-ai/ai-task-master/main/.claude/commands/feature.md

Clone the repo

git clone --depth 1 https://github.com/developerz-ai/ai-task-master

Made for: Claude Code.

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/commands/developerz-ai/ai-task-master/feature/github.svg)](https://agentmods.dev/commands/developerz-ai/ai-task-master/feature)

Your own site

<a href="https://agentmods.dev/commands/developerz-ai/ai-task-master/feature"><img src="https://agentmods.dev/badge/commands/developerz-ai/ai-task-master/feature/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/commands/developerz-ai/ai-task-master/feature"><img src="https://agentmods.dev/badge/commands/developerz-ai/ai-task-master/feature.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 76 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

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

Security scan A 1 finding. 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.00076	$0.05157
Opus 5.5	$0.00030	$0.02063
Sonnet 5.5	$0.00015	$0.01031
Haiku 4.5	$0.00008	$0.00516

Measured 4d ago against content hash 41fe318f140a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

feature scanned grade A with 1 finding 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.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

**OpenRouter only** — OpenAI-compatible, no Anthropic SDK ever; all inference through `credentials/` (`OPENROUTER_API_KEY`). A target repo's `CLAUDE.md`/`AGENTS.md` is a *coding-style* signal for subagent prompts, **not*

.claude/commands/feature.md · 132 lines

How it starts

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

/feature

You are a senior engineer on the aitm team. aitm is a thin CLI that orchestrates AI coding agents (an Orchestrator driving Planner/Worker/Reviewer subagents-as-tools) to turn a goal into commits and PRs — inference through OpenRouter only, git/PR work through the gh CLI. Read CLAUDE.md before designing anything.

Done means merged and green under both runtimes — nothing less counts. understand → reproduce → explore → slice → build → gate → PR → merged → the symptom re-checked with a real run → issues and docs left true. A green bun test alone is not done (the Node run is what CI enforces); an open PR is not done. Nothing here deploys: aitm ships as the npm package @developerz.ai/aitm, and a publish is an explicit, user-requested, irreversible step — the normal arc ends at merged. Report what you actually verified, not what you assume happened.

Request

$ARGUMENTS

The prompt is the context — read the intent. How autonomous to be, how big the scope, which modules, whether to confirm before merging, whether to cut a release: infer it from the words. "Just ship it" → run start-to-finish, decide everything yourself, merge on green; surface decisions in the issue and PR body instead of asking. A tentative or exploratory ask → clarify what is genuinely ambiguous and let the user review before you merge. Don't make the user configure you. The flow is a map, not a checklist to recite — but always stop for a true blocker: an irreversible npm publish, a destructive git/gh action against a real repo, anything in Out of scope (mailbox, aitm-as-MCP-server, inbound HTTP, containerization), an external dep you can't satisfy.

Pick the PR mode before you brief anyone. Slice-per-PR (default) — one concern per PR, merged one at a time. One fat PR is the user's call for a coherent sweep; path-disjointness still governs the build (it is how parallel agents avoid clobbering each other), it just stops governing the commit, and the PR body then carries the finding-by-finding ledger.

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

4d ago Changed 41fe318f140a
2mo ago First seen · 132 lines · 76 tokens per session scan A 00baa64c4a91

Subscribe to this mod's changes

feature is a command published in the GitHub repository developerz-ai/ai-task-master (5 stars, last pushed 3d ago), licensed MIT. It adds 76 tokens to every session and 5,157 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Building agents LLM Planning ai-agent autonomous-agent bun cli github-automation

feature next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
featuredeveloperz-ai/ai-task-master	Command	5	3d ago	MIT	A	76	Claude Code
fix-issuescan1357/oh-my-pi	Command	38k	yesterday	MIT	A	0	Claude Code
triagecan1357/oh-my-pi	Command	38k	yesterday	MIT	A	0	Claude Code
releasecan1357/oh-my-pi	Command	38k	yesterday	MIT	A	0	Claude Code
cleanupcan1357/oh-my-pi	Command	38k	yesterday	MIT	A	0	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code

ai-task-master: Command for Claude Code