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 sumimakito/roll --skill roll-pushgit clone --depth 1 https://github.com/sumimakito/rollWrote 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/sumimakito/roll/roll-push)<a href="https://agentmods.dev/skills/sumimakito/roll/roll-push"><img src="https://agentmods.dev/badge/skills/sumimakito/roll/roll-push/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/sumimakito/roll/roll-push"><img src="https://agentmods.dev/badge/skills/sumimakito/roll/roll-push.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.00036 | $0.00358 |
| Opus 5.5 | $0.00014 | $0.00143 |
| Sonnet 5.5 | $0.00007 | $0.00072 |
| Haiku 4.5 | $0.00004 | $0.00036 |
Grade A, and why
roll-push 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.
What it actually says
roll-push
Push the PR head only after roll-verify passes. Use confirmed STRATEGY:
merge uses normal push; rebase requires --force-with-lease. Never use
bare --force.
Procedure
- Identify head:
git rev-parse --abbrev-ref HEAD. - Protected-branch guard: if head matches
main,master,prod,production,release,develop,dev,release/*, orhotfix/*case-insensitively, stop and require explicit "yes, push " confirmation. IfSTRATEGY=rebase, state that this is a force-push. - Push:
STRATEGY=merge:git push origin <head-branch>.STRATEGY=rebase:git push --force-with-lease origin <head-branch>.- New remote branch: use
git push -u origin <head-branch>only when no rewrite is needed; otherwise include the lease.
- If push is rejected, report remote movement and let
rollre-fetch and re-resolve. Do not escalate to bare--force.
Stop Rules
- No push before verification passes.
- No bare
--force. - No protected-looking branch push without explicit confirmation.
- No observe step after rejected push.
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 · 32 lines · 36 tokens per session scan A 735be062ab61
roll-push is a skill published in the GitHub repository sumimakito/roll (2 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 358 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-31.
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.