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/chriswritescode-dev/opencode-forge/loop-statusgit clone --depth 1 https://github.com/chriswritescode-dev/opencode-forgeWhat 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.00000 | $0.00224 |
| Opus 5 | $0.00000 | $0.00112 |
| Sonnet 5 | $0.00000 | $0.00045 |
| Haiku 4.5 | $0.00000 | $0.00022 |
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 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
Check the status of all loops.
Step 1: List Active Loops
Run loop-status with no arguments to list all active loops for the current project.
Step 2: Get Detailed Status
For each active loop found, run loop-status with the loop name to get detailed status. Token counts, iterations, last output.
Step 3: Report
Present a summary showing:
- Total number of active loops
- For each loop: name, status, and any additional details
If no loops are active, report that there are no active loops.
Accessing a Completed Loop's Work
A completed loop's worktree is cleaned up, so the worktree directory no longer exists. The work is preserved on a local git branch that is never deleted. To inspect or switch to it, use the branch forge/<loop-name> (the loop name is slugified: lowercased with non-alphanumeric characters replaced by hyphens). Check out that branch directly rather than trying to cd into the pruned worktree path.
$ARGUMENTS
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 · 24 lines · 0 tokens per session scan A e3a5368faf47
loop-status is a command published in the GitHub repository chriswritescode-dev/opencode-forge (11 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 224 tokens. 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.