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 skills add eltonio450/rondo --skill rondo-resume-ticketgit clone --depth 1 https://github.com/eltonio450/rondoWrote 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/skills/eltonio450/rondo/rondo-resume-ticket)<a href="https://agentmods.dev/skills/eltonio450/rondo/rondo-resume-ticket"><img src="https://agentmods.dev/badge/skills/eltonio450/rondo/rondo-resume-ticket/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/skills/eltonio450/rondo/rondo-resume-ticket"><img src="https://agentmods.dev/badge/skills/eltonio450/rondo/rondo-resume-ticket.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.00031 | $0.00564 |
| Opus 5 | $0.00015 | $0.00282 |
| Sonnet 5 | $0.00006 | $0.00113 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
rondo-resume-ticket 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.
How it starts
The opening of the file, as written. The whole thing — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resume a Rondo ticket
Rondo dispatch is at least once. Before doing work, determine whether another dispatch or PR already exists. Never assume a timeout means the remote agent stopped.
Reconstruct state
- Read repository guidance and the complete target ticket: frontmatter, mission, steps, decisions, and progress.
- Inspect current base-branch code and recent relevant changes; ticket plans can become stale.
- Resolve the branch from the machine JSON block in the open Issue labelled
rondo-registry. If no mapping exists, use the configured branch prefix (defaultrondo/<slug>). - Search open PRs on that exact branch in the host repository. A same-named fork branch is not the same head.
- Inspect provider state when the last dispatch timed out or failed ambiguously.
If an open, relevant PR already exists, do not start another step. Continue/review that work or report the inconsistency.
Pause semantics
paused: true: stop unless a human explicitly authorizes unpause.- future
paused: YYYY-MM-DD: stop until that date. - date today or earlier: remove the key and matching
[resume: DATE]suffix before progressing. paused: false: unpaused; remove it for clarity when editing.
Choose one outcome
- Progress: implement one reviewable next step; insert progress/decisions at the top; create or update the single matching PR touching the ticket.
- Pause: set a valid pause, record reason/trigger/owner, and create or update the single ticket-only PR.
- Done: promote durable knowledge, then remove or explicitly archive the ticket in the single matching PR.
- No-op: record blocker, need, and owner in the single ticket-only PR; do not repeat the same no-op indefinitely.
Use the registry branch as head and configured base branch as target. Work on only this ticket. Ensure exactly one relevant PR exists—reuse it on retry—and remember that the runner does not verify this; your compliance preserves the protocol.
Re-scope or retire
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 · 41 lines · 31 tokens per session scan A 6055877582f1
rondo-resume-ticket is a skill published in the GitHub repository eltonio450/rondo (23 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 564 once invoked, about $0.0002 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-30.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.