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/doncheli/don-cheli-sddWrote 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/doncheli/don-cheli-sdd/bucle-estado)<a href="https://agentmods.dev/commands/doncheli/don-cheli-sdd/bucle-estado"><img src="https://agentmods.dev/badge/commands/doncheli/don-cheli-sdd/bucle-estado.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.00007 | $0.00051 |
| Opus 5 | $0.00003 | $0.00026 |
| Sonnet 5 | $0.00001 | $0.00010 |
| Haiku 4.5 | $0.00001 | $0.00005 |
Grade A, and why
bucle-estado 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
/bucle-estado
Uso
/bucle-estado
Muestra el estado actual del bucle: historias completadas, pendientes y patrones aprendidos.
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 · 14 lines · 7 tokens per session scan A e313a730744a
bucle-estado is a command published in the GitHub repository doncheli/don-cheli-sdd (57 stars, last pushed 29d ago), licensed Apache-2.0. It adds 7 tokens to every session and 51 once invoked, about $0.0000 per session on Opus 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-03.
Other commands, from other repositories
insert-phase
Insert urgent work as decimal phase (e.g., 72.1) between existing phases.
remove-phase
Remove a future phase from roadmap and renumber subsequent phases.
add-todo
Capture idea or task as todo from current conversation context.
audit-milestone
Audit milestone completion against original intent before archiving.
new-milestone
Start a new milestone cycle — update PROJECT.md and route to requirements.
backlog
Manage backlog items — ideas not ready for active planning. Add, review, promote, or remove.