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/MadaraUchiha-314/the-loopWrote 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/madarauchiha-314/the-loop/work-status)<a href="https://agentmods.dev/commands/madarauchiha-314/the-loop/work-status"><img src="https://agentmods.dev/badge/commands/madarauchiha-314/the-loop/work-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/madarauchiha-314/the-loop/work-status"><img src="https://agentmods.dev/badge/commands/madarauchiha-314/the-loop/work-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.00031 | $0.00503 |
| Opus 5.5 | $0.00012 | $0.00201 |
| Sonnet 5.5 | $0.00006 | $0.00101 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
work-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 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.
What it actually says
the-loop: work-status $ARGUMENTS
Report where a work item stands. Read-only — this command inspects and summarizes; it does not change anything.
Read the the-loop skill and reference/workflow.md for the phase model.
Steps
-
Locate the spec. Resolve
$ARGUMENTStodocs/specs/<id>/. If nothing is found, check for adraft-*folder (pre-ticket) and say so. -
Read the artifacts (whichever exist):
requirements.md/bugfix.md,design.md,tasks.md,work-item-state.jsonand the records underevidence/. Also read the ticket's current phase label if the ticketing integration is available.requirements.mdandbugfix.mdare two accepted names for the same phase-1 artifact — if both are on disk, say so: therequirements-definitiongate blocks on it (decision-045). -
Summarize:
- Phase — from
work-item-state.json's current node and the ticket label (flag any mismatch). - Spec status — which of requirements/design/tasks exist and their
status(draft / approved) and approvers. - Task progress — count of
- [x]vs- [ ]intasks.md(the-loop keeps these current as tasks complete), and which tasks are outstanding. - Gates passed — which records under
evidence/exist and what they say, and any pending review/human action. - Next step — the command to move forward (
create-design/create-tasks-plan/execute-tasks/finish-tasks).
- Phase — from
-
Present it as a concise, prioritized summary (mermaid where a diagram helps). Do not modify any file or ticket.
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 Changed · +1 lines · +6 tokens per session 9125d7a35b8b
- 1mo ago Changed 9613da4f6fb1
- 1mo ago First seen · 39 lines · 25 tokens per session scan A 1298cc57dd8b
work-status is a command published in the GitHub repository MadaraUchiha-314/the-loop (7 stars, last pushed 2d ago), licensed MIT. It adds 31 tokens to every session and 503 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-31.
Other commands, from other repositories
close
They operate it without you.
okr
Create or review OKRs (Objectives and Key Results).
project-health
Assess overall project health across code quality, tests, docs, and activity.
retro
Run a sprint retrospective with data-driven insights from git history.
sprint-health
Check current sprint health and identify risks.
sprint-plan
Plan a sprint by analyzing backlog, estimating capacity, and selecting work.