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/Vvlladd/qrspi-orchestratorWrote 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/vvlladd/qrspi-orchestrator/qrspi-resume)<a href="https://agentmods.dev/commands/vvlladd/qrspi-orchestrator/qrspi-resume"><img src="https://agentmods.dev/badge/commands/vvlladd/qrspi-orchestrator/qrspi-resume/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/vvlladd/qrspi-orchestrator/qrspi-resume"><img src="https://agentmods.dev/badge/commands/vvlladd/qrspi-orchestrator/qrspi-resume.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.00011 | $0.00328 |
| Opus 5 | $0.00005 | $0.00164 |
| Sonnet 5 | $0.00002 | $0.00066 |
| Haiku 4.5 | $0.00001 | $0.00033 |
Grade A, and why
qrspi-resume 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 12d 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
Resume QRSPI Pipeline
The pipeline was interrupted or a new session started. Resume from the last checkpoint.
Recovery Process
- Read progress.md to find the last completed phase and activity
- Read tasks.json to find the current task status
- Check reports/ to verify which phase deliverables exist
- Check git log for the latest QRSPI commits
Determine Resume Point
Based on the state:
- If
reports/01-requirements.mdexists but not02-exploration.md: Resume at Phase 2 (Research) - If
02-exploration.mdexists but not03-design.md: Resume at Phase 3 (Design) - If
03-design.mdexists but nottasks.jsonor it's empty: Resume at Phase 4 (Plan) - If
tasks.jsonhas tasks with statuspendingorin_review: Resume at Phase 5 (Implementation) - If all tasks are
approved: Resume at Phase 6 (PR Creation)
Resume
Present the current state to the human:
- "Pipeline was at Phase N: [Phase Name]. Last activity: [description]. Ready to continue?"
Wait for human confirmation before proceeding. Then follow the same pipeline rules as /qrspi from the appropriate phase.
IMPORTANT: Run the startup ritual (read progress, check git, run tests) before doing any work.
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.
- 12d ago First seen · 35 lines · 11 tokens per session scan A ff9d69a1e003
qrspi-resume is a command published in the GitHub repository Vvlladd/qrspi-orchestrator (6 stars, last pushed 11d ago), licensed MIT. It adds 11 tokens to every session and 328 once invoked, about $0.0001 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-08-31.
Other commands, from other repositories
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
handoff
Export a Waybill Bundle by default, or import one when requested.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.