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-status)<a href="https://agentmods.dev/commands/furkantokkan/agent-foundry/task-status"><img src="https://agentmods.dev/badge/commands/furkantokkan/agent-foundry/task-status/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-status"><img src="https://agentmods.dev/badge/commands/furkantokkan/agent-foundry/task-status.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.00023 | $0.00243 |
| Opus 5.5 | $0.00009 | $0.00097 |
| Sonnet 5.5 | $0.00005 | $0.00049 |
| Haiku 4.5 | $0.00002 | $0.00024 |
Grade A, and why
task-status 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 5d 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 Status
Use the task-status Codex skill for this request.
Treat the complete block below as one raw task-status input. Preserve exact task IDs, contract paths, ordering, and the repository selector.
Report current phase, task-owned changed paths, recorded test evidence and
freshness, unresolved and verified defect counts/IDs, one blocker, any genuine
user decision, and one next command per task. Any already-recorded unresolved,
blocked, or stale defect points to /task-cycle <ID>; new unrecorded feedback
points to /task-bug [<ID>] "<feedback>". Read lifecycle state from contract.md;
legacy status.md is read-only compatibility input. Do not run tests/builds,
mutate Unity, start or interrupt agents, write state, start a task cycle, close
tasks, or change VCS/external tracker state.
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.
- 5d ago First seen · 25 lines · 23 tokens per session scan A 153c1f2d6f4e
task-status is a command published in the GitHub repository furkantokkan/agent-foundry (10 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 243 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).