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.
npx agentmods add commands/ayoubben18/ab-method/start-taskgit clone --depth 1 https://github.com/ayoubben18/ab-methodWhat 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 | $0.00000 | $0.00688 |
| Opus 5 | $0.00000 | $0.00344 |
| Sonnet 5 | $0.00000 | $0.00138 |
| Haiku 4.5 | $0.00000 | $0.00069 |
Grade A, and why
start-task 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 2d 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Start Task
Description
Run an existing task autonomously to completion — /resume-task with the /goal philosophy. Each remaining mission runs in a subagent that follows tdd and updates the progress tracker itself; the parent verifies tests and commits after every finished mission. Starts immediately on invocation — no "Proceed?" prompt — then no prompts until done (or something goes red).
Usage
/start-task [task-name]
Behavior
Loads and executes the start-task workflow from .ab-method/core/start-task.md
This workflow will:
- Identify the task and read its
progress-tracker.md(single source of truth) - Gate on vagueness — any mission too fuzzy to run without judgment calls gets grilled before the run, never mid-run
- Announce the plan (missions, parallel groups, commit-per-mission) and start immediately — no "Proceed?"; invoking the command is the consent
- Run every remaining mission in a subagent through the
tdddiscipline; the subagent checks off its mission and appends its technical summary to the tracker - Verify the test suite after each mission, then commit (one commit per mission, one per
[pp-x]group) - Run
review-implementationafter the last mission (autonomous mode) — three critics (cleaner-architecture, slop-defender, reusability-inspector) on the task diff; safe fixes auto-applied (tests-green-gated, own commit), everything written todocs/tasks/<task>/review.mdfor you to read afk - Stop loudly on red — never commits broken work, never starts the next mission on a broken state
/start-task vs /resume-task
/start-task— trust the roadmap, walk away, review commits instead of missions/resume-task— stay in the loop, review each mission before moving on
Workflow Details
- No confirmation — starts immediately, then autonomous — no "Proceed?" gate, no prompting between missions
- Group-aware —
[pp-x]missions run concurrently in subagents; siblings skip the tracker (the parent merges their summaries) to avoid write conflicts - Green tests gate every commit — a red feedback loop takes priority over progress, exactly like
/goal - Executor, not producer — missions are defined by
/create-task//extend-task; this workflow only runs them - A black box doesn't stop the run — a mission marked
⚠️ UQ-nbuilds the placeholder recorded inunresolved-questions.mdand keeps going; the run never answers a parked question, and every open one it built on is listed in the announcement and the final report
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.
- 2d ago First seen · 50 lines · 0 tokens per session scan A ccd87e6b11cd
start-task is a command published in the GitHub repository ayoubben18/ab-method (187 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 688 tokens. 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-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.