Borrowing it
Nothing to install: this file belongs to yapota2018/affaan-m-everything-claude-code. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/yapota2018/affaan-m-everything-claude-code/main/.opencode/commands/loop-status.mdgit clone --depth 1 https://github.com/yapota2018/affaan-m-everything-claude-codeWrote 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/yapota2018/affaan-m-everything-claude-code/loop-status)<a href="https://agentmods.dev/commands/yapota2018/affaan-m-everything-claude-code/loop-status"><img src="https://agentmods.dev/badge/commands/yapota2018/affaan-m-everything-claude-code/loop-status.svg" alt="Measured on agentmods" 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.00000 | $0.00105 |
| Opus 5 | $0.00000 | $0.00053 |
| Sonnet 5 | $0.00000 | $0.00021 |
| Haiku 4.5 | $0.00000 | $0.00011 |
Grade A, and why
loop-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 6d 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.
This is a copy
100% identical to loop-status — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Loop Status Command
Inspect active loop state, progress, and failure signals.
Usage
/loop-status [--watch]
What to Report
- active loop pattern
- current phase and last successful checkpoint
- failing checks (if any)
- estimated time/cost drift
- recommended intervention (continue/pause/stop)
Watch Mode
When --watch is present, refresh status periodically and surface state changes.
Arguments
$ARGUMENTS:
--watchoptional
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.
- 6d ago First seen · 25 lines · 0 tokens per session scan A 24181d139215
loop-status is a command published in the GitHub repository yapota2018/affaan-m-everything-claude-code (4 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 105 tokens. A static security scan graded it A with 0 findings. It is 100% identical to loop-status, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.