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.
git clone --depth 1 https://github.com/furkantokkan/agent-foundryWrote 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/commands/furkantokkan/agent-foundry/task-bug)<a href="https://agentmods.dev/commands/furkantokkan/agent-foundry/task-bug"><img src="https://agentmods.dev/badge/commands/furkantokkan/agent-foundry/task-bug/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/commands/furkantokkan/agent-foundry/task-bug"><img src="https://agentmods.dev/badge/commands/furkantokkan/agent-foundry/task-bug.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.00029 | $0.00304 |
| Opus 5.5 | $0.00012 | $0.00122 |
| Sonnet 5.5 | $0.00006 | $0.00061 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
task-bug 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.
What it actually says
Task Bug
Use the task-bug Codex skill for this request.
Forward the complete block as one raw intake. Preserve the optional identity, quoted feedback, attachments, logs, references, and repository selector.
The adapter performs no task matching, lifecycle mutation, document creation,
implementation, verification, closure, commit, or push itself. The skill owns
routing: confirmed observable failures go to task-cycle; revision/status
feedback is not a defect. With an explicit task it returns
CONTRACT_CHANGE_REQUIRED or STATUS_QUERY without lifecycle dispatch;
without an owner it may go once to create-task as a planned change.
If a proven live writer already owns the matched task or the new task's paths,
route through agent-orchestration as WAITING_FOR_OWNER; retain the
raw feedback and execution authorization, then resume automatically after the
owner releases.
A D-xxx mentioned in conversation or a handoff is only a candidate. Neither
this adapter nor the intake may announce confirmed reuse, recurrence, reopen,
root cause, or a chosen fix before task-cycle checks canonical records.
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 Changed c71f4409aa24
- 5d ago First seen · 31 lines · 29 tokens per session scan A 6e5c747e6385
task-bug is a command published in the GitHub repository furkantokkan/agent-foundry (10 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 304 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-09-25.
Other commands, from other repositories
speckit.companion.doctor
Report on a spec's run health — unfinished steps, unjournaled tasks, step bleed, drift you can judge, a step that closed having verified nothing, a step that closed without the file it promised, and why completion did not land (read-only, retroactive, never halts).
backlog
The project layer: milestones, epics, and user stories with refusing controllers — spec-seeded, sprint-ready.
status
The state of play, computed fresh: branch, dirty files, the active sprint, open work, index freshness.
debug
Systematic debugging with hypotheses and evidence gathering.
debug
Structured debugging with parallel investigation agents.
validated
Record durable, git-tracked evidence that a ticket was actually validated (interactive-session twin of the governor's auto-promotion).