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 skills add makifbaysal/tasktrooper --skill stepwise-task-executiongit clone --depth 1 https://github.com/makifbaysal/tasktrooperWrote 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/skills/makifbaysal/tasktrooper/stepwise-task-execution)<a href="https://agentmods.dev/skills/makifbaysal/tasktrooper/stepwise-task-execution"><img src="https://agentmods.dev/badge/skills/makifbaysal/tasktrooper/stepwise-task-execution/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/skills/makifbaysal/tasktrooper/stepwise-task-execution"><img src="https://agentmods.dev/badge/skills/makifbaysal/tasktrooper/stepwise-task-execution.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.00033 | $0.01822 |
| Opus 5.5 | $0.00013 | $0.00729 |
| Sonnet 5.5 | $0.00007 | $0.00364 |
| Haiku 4.5 | $0.00003 | $0.00182 |
Grade A, and why
stepwise-task-execution 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 8d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stepwise Task Execution
Overview
An implementation task is never done in one big move. You understand the task completely, break it into an ordered list of small steps, and drive each step through its own test-and-commit cycle. This is the master workflow every developer role follows on every task; the individual disciplines it orchestrates live in their own skills.
Core principle: Small, verified, committed steps beat one large uncommitted change every time — for correctness, for review, and for cheap revisions.
REQUIRED SUB-SKILLS: tdd-workflow (each step is test-first), incremental-commits (commit each green step), verify-before-done (prove it works before handoff), root-cause-debugging (when a step or a revision fails).
When to Use
Every task that changes product code — features, bug fixes, refactors, revisions. Never skip the decomposition because a task "looks small": unexamined small tasks are where scope and edge cases hide.
digraph stepwise {
"Task picked up" [shape=box];
"Requirements clear?" [shape=diamond];
"Ask numbered questions\n(add_task_comment)" [shape=box];
"Decompose into steps" [shape=box];
"Execute one step\n(test -> code -> verify -> commit)" [shape=box];
"More steps?" [shape=diamond];
"Verify whole task\n+ every AC" [shape=box];
"Handoff to code_review" [shape=doublecircle];
"Task picked up" -> "Requirements clear?";
"Requirements clear?" -> "Ask numbered questions\n(add_task_comment)" [label="no"];
"Requirements clear?" -> "Decompose into steps" [label="yes"];
"Decompose into steps" -> "Execute one step\n(test -> code -> verify -> commit)";
"Execute one step\n(test -> code -> verify -> commit)" -> "More steps?";
"More steps?" -> "Execute one step\n(test -> code -> verify -> commit)" [label="yes"];
"More steps?" -> "Verify whole task\n+ every AC" [label="no"];
"Verify whole task\n+ every AC" -> "Handoff to code_review";
}
Autonomy: you do NOT wait for human approval on your plan. Understand, decompose, build, verify, and move the task to code_review yourself. No human approves your plan: the human gates are analiz_review (before code exists) and human_uat (after QA and PM), never your step list.
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.
- 8d ago First seen · 113 lines · 33 tokens per session scan A 431547f361a1
stepwise-task-execution is a skill published in the GitHub repository makifbaysal/tasktrooper (113 stars, last pushed yesterday), licensed Apache-2.0. It adds 33 tokens to every session and 1,822 once invoked, about $0.0001 per session on Opus 5.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-10-05.
Other skills, from other repositories
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contextual-commit
Write contextual commits that capture intent, decisions, and constraints alongside code changes. Use when committing code, finishing a task, or when the user asks to commit. Extends Conventional Commits with structured action lines in the commit body that preserve WHY code was written, not just WHAT changed.
git-workflow-management
Git workflow automation skill for commit message generation, branch management, pre-commit checks, and change history analysis.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.