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-installgit 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-install)<a href="https://agentmods.dev/skills/eltonio450/rondo/rondo-install"><img src="https://agentmods.dev/badge/skills/eltonio450/rondo/rondo-install/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-install"><img src="https://agentmods.dev/badge/skills/eltonio450/rondo/rondo-install.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.00736 |
| Opus 5.5 | $0.00012 | $0.00294 |
| Sonnet 5.5 | $0.00006 | $0.00147 |
| Haiku 4.5 | $0.00003 | $0.00074 |
Grade A, and why
rondo-install 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 2mo 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rondo install
Use this skill when a human asks to install, update, suspend, or inspect Rondo in a repository.
Guardrails
- Start with read-only discovery and preserve unrelated changes.
- Ask for
<RONDO_REF>, a reviewed immutable 40-character Rondo commit SHA. Never usemainor assume a version tag exists. - Respect the host's branch protection and PR policy. Do not insist on direct commits.
- Never set, read, print, or request a secret value. Print the
gh secret set ...command for the human. - Do not run a new remote workflow until its file has been pushed and, when required, merged to the default branch.
- Only Cursor and generic HTTP adapters are shipped.
- Dispatch is at least once. The runner requests but does not verify exactly one relevant PR, reused on retry.
- Stop before destructive or unapproved external mutation.
Discover
Inspect:
- repository root, current branch, dirty files, and contributor/agent guidance;
- default branch, remote identity, branch/Actions policy, and
ghauthentication; - ticket directory,
rondo.prompt.md,rondo*.ymlworkflows, installed skills, and registry Issue/label; - who may install GitHub Apps, create labels, set secrets, and require checks;
- whether outbound prompt/repository metadata may go to Cursor or the proposed HTTP receiver.
Show any existing Rondo artifact before changing it.
Source instructions
Prefer an already reviewed local Rondo checkout at <RONDO_REF>. Otherwise, after the human supplies that SHA, retrieve the raw files at exactly:
https://raw.githubusercontent.com/eltonio450/rondo/<RONDO_REF>/INSTALL.md
https://raw.githubusercontent.com/eltonio450/rondo/<RONDO_REF>/install/<brick-file>
Do not fetch from main. Read INSTALL.md and every selected brick completely.
Recommended reference profile
Offer bricks 1–6, with skills optional:
- flat ticket directory, with optional
.gitkeepfor discoverability; - bundled prompt or explicit host override;
- one GitHub Issue registry;
- serialized GitHub Actions scheduler;
- Cursor or HTTPS adapter;
- ticket-validation CI;
- optional standalone skills.
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.
- 2mo ago First seen · 70 lines · 31 tokens per session scan A 3b62f992bc12
rondo-install is a skill published in the GitHub repository eltonio450/rondo (23 stars, last pushed 3mo ago), licensed MIT. It adds 31 tokens to every session and 736 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 skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.