Borrowing it
Nothing to install: this file belongs to goern/forgejo-mcp. 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/goern/forgejo-mcp/main/.claude/commands/team/dev-loop.mdgit clone --depth 1 https://github.com/goern/forgejo-mcpWrote 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/goern/forgejo-mcp/dev-loop)<a href="https://agentmods.dev/commands/goern/forgejo-mcp/dev-loop"><img src="https://agentmods.dev/badge/commands/goern/forgejo-mcp/dev-loop/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/goern/forgejo-mcp/dev-loop"><img src="https://agentmods.dev/badge/commands/goern/forgejo-mcp/dev-loop.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.00033 | $0.05428 |
| Opus 5.5 | $0.00013 | $0.02171 |
| Sonnet 5.5 | $0.00007 | $0.01086 |
| Haiku 4.5 | $0.00003 | $0.00543 |
Grade A, and why
Team: Dev Loop 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.
The source is not reproduced here
Licensed GPL-3.0
The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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 First seen · 457 lines · 33 tokens per session scan A 38a947c99bd2
Team: Dev Loop is a command published in the GitHub repository goern/forgejo-mcp (148 stars, last pushed today), licensed GPL-3.0. It adds 33 tokens to every session and 5,428 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-30.
Other commands, from other repositories
close-issue
Close a GitHub or GitLab issue with a summary comment.
dashboard
Phase 3 monitoring — System health, execution insights, and velocity analytics.
run
Execute an approved PRD using feature branch workflow (v7.0). This command generates briefs, auto-reviews them, allows user iteration, and then orchestrates execution.
implement-evidence-asks
Read by /implement Phase 1 (D-CMD-REF-HAND). "The grammar below", "the exception grammar above" and "the record above" name sections of this file. Any other "above" means the Phase 1 text before the step that sent you here.
implementation-commands
Commands for tracking implementation of recommendations, updating progress, analyzing blockers, and running weekly accountability check-ins. These commands operate on the implementation tracking layer and read from and write to the active and history memory layers.
triage-sweep
Sweep a repo's TRIAGE-labeled backlog — vet every issue against the code, fix the easy ones in one cleanup PR, and label the rest priority → tier → size → kind → area → signals, with epics grouped and ranked. Repo-agnostic: discovers each repo's label taxonomy at runtime.