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/fusengine/agents/run-tasksgit clone --depth 1 https://github.com/fusengine/agentsWhat 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.00023 | $0.00398 |
| Opus 5 | $0.00012 | $0.00199 |
| Sonnet 5 | $0.00005 | $0.00080 |
| Haiku 4.5 | $0.00002 | $0.00040 |
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 yesterday.
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.
What it actually says
Run GitHub Issue Tasks
Execute GitHub issue with complete EPCT workflow:
-
Fetch Issue Details:
gh issue view $ARGUMENTSExtract:
- 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
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.
- yesterday First seen · 75 lines · 23 tokens per session scan A 1bead1721605
run-tasks is a command published in the GitHub repository fusengine/agents (25 stars, last pushed 28d ago), licensed MIT. It adds 23 tokens to every session and 398 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-30.
Other commands, from other repositories
burn-rate
Compute the recent 7-day spend trend (burn rate) from daily sessions and per-session cost.
profile
Coordinate a reproducible Java profiling and optimization lifecycle.
update-issue
Update an issue description with structured, evidence-backed content.
publish-skill
Sync a marketplace skill to the documentation site. Creates skill detail pages (EN/ZH), updates the marketplace index, and updates docs.json navigation.
deploy
Deploy Solana program (devnet first, then mainnet).
generate-idl-client
Generate TypeScript client from Solana program IDL using Codama or Anchor.