A command that takes a GitHub issue number and works through its requirements, then creates a code branch, commit, and pull request. It follows four stages: explore, plan, code, and test.

Use it to implement a GitHub issue from start to finish, including checking the issue, testing the changes, opening a pull request, and commenting on the issue with the link.

It removes the manual steps of turning an issue into a proposed code change and linking that change back to the issue.

run-tasks — Command for Claude Code by fusengine/agents

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/fusengine/agents

Made for: Claude Code.

Or install fuse-ai-pilot, the plugin that ships this one along with the rest of its 18 skills, 12 commands, 9 agents, 5 hooks.

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/fusengine/agents/run-tasks/github.svg)](https://agentmods.dev/commands/fusengine/agents/run-tasks)

Your own site

<a href="https://agentmods.dev/commands/fusengine/agents/run-tasks"><img src="https://agentmods.dev/badge/commands/fusengine/agents/run-tasks/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/fusengine/agents/run-tasks"><img src="https://agentmods.dev/badge/commands/fusengine/agents/run-tasks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 398 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.

Model	Per session	Once invoked
Fable 5.1	$0.00023	$0.00398
Opus 5.5	$0.00009	$0.00159
Sonnet 5.5	$0.00005	$0.00080
Haiku 4.5	$0.00002	$0.00040

Measured 1mo ago against content hash 1bead1721605, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

run-tasks 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 1mo 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.

plugins/ai-pilot/commands/run-tasks.md · 75 lines

What it actually says

Run GitHub Issue Tasks

Execute GitHub issue with complete EPCT workflow:

Fetch Issue Details:
```
gh issue view $ARGUMENTS
```
Extract:
- Issue title and description
- Acceptance criteria
- Labels and priority
- Related issues/PRs
Execute EPCT: Run /epct [ISSUE_TITLE] workflow:

EXPLORE: Understand affected components PLAN: Design solution CODE: Implement changes TEST: Validate implementation

Create Branch:

git checkout -b issue-$ISSUE_NUMBER-[slug]

Commit Changes:

git commit -m "$(cat <<'EOF'
feat: [ISSUE_TITLE]

Fixes #$ISSUE_NUMBER

- [Change 1]
- [Change 2]


EOF
)"

Create PR:

gh pr create --title "Fixes #$ISSUE_NUMBER: [TITLE]" --body "$(cat <<'EOF'
## Summary
Resolves #$ISSUE_NUMBER

## Changes
[List of changes]

## Test Plan
[How tested]

EOF
)"

Link Issue:

gh issue comment $ISSUE_NUMBER --body "PR created: [PR_URL]"

Arguments:

$ARGUMENTS = GitHub issue number

Example Usage:

/run-tasks 42 → Execute issue #42 with full workflow

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.

1mo ago First seen · 75 lines · 23 tokens per session scan A 1bead1721605

Subscribe to this mod's changes

run-tasks is a command published in the GitHub repository fusengine/agents (31 stars, last pushed 3d ago), licensed MIT. It adds 23 tokens to every session and 398 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-08-30.

Claude Code Commits Git and workflow Project management claude-agent claude-agents claude-code-plugin claude-skills claudecode

migrate-ledger

(Ledger) Move a pre-2.0 in-repo Agile-Ledger/ folder into the ledger repo, then clean the code repo.

nunoamorim99/agile-ledger · 30 tokens

ledger-commit

(Ledger) Review and commit the ledger repo's changes (push only on confirmation).

nunoamorim99/agile-ledger · 18 tokens

register-repo

(Ledger) Register a code repo into the ledger — its folder + the eight files + a Registry row.

nunoamorim99/agile-ledger · 22 tokens

init-ledger

(Ledger) Create the ledger repository — Registry + Config — the one-time setup.

nunoamorim99/agile-ledger · 17 tokens

flow

Universal workflow entry point. Use /flow for skill-driven GitHub development. Verbs: start, commit, pr, review, address, merge, resolve, release, status, learn, setup, explain, debug, design, brainstorm, issue.

synaptiai/synapti-marketplace · 56 tokens

weekly-review

Produce a weekly review from the evidence in the repository and the workspace: commits and pull requests merged or open, issues closed and opened, decisions logged, research log entries, action items done and overdue, and what stalled, then a short plan for next week; written to a dated file so reviews accumulate. Use…

KhaledSaeed18/dotclaude · 97 tokens