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-resolvegit 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-resolve)<a href="https://agentmods.dev/skills/sumimakito/roll/roll-resolve"><img src="https://agentmods.dev/badge/skills/sumimakito/roll/roll-resolve/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-resolve"><img src="https://agentmods.dev/badge/skills/sumimakito/roll/roll-resolve.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.00029 | $0.00368 |
| Opus 5.5 | $0.00012 | $0.00147 |
| Sonnet 5.5 | $0.00006 | $0.00074 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
roll-resolve 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-resolve
Integrate base using the confirmed STRATEGY. Resolve only conflicts that can
preserve both sides' intent. For semantic conflicts, stop and hand off.
Procedure
- Fetch and integrate base:
rebase:git fetch origin <base> && git rebase origin/<base>merge:git fetch origin <base> && git merge origin/<base>Do not choose strategy here;rollalready confirmed it.
- Classify conflicts:
- Auto-resolve: lockfiles, generated files, import ordering, and strictly non-overlapping hunks where keeping both preserves intent.
- Take-over: overlapping logic edits, semantic conflicts, or any resolution requiring behavior choice or intent guessing.
- Auto-resolve only safe conflicts. Regenerate lockfiles when practical; state what changed and why intent is preserved.
- For take-over conflicts, stop. Show file/hunk and why it is unsafe; let the user resolve it or give explicit per-file instructions. Wait for completion.
- When conflict-free, continue:
git rebase --continueor commit the merge. - Output a clean tree ready for
roll-verify, or a handoff list of unresolved take-over conflicts.
Stop Rules
- Do not edit semantic conflicts without explicit per-file instruction.
- Do not treat handoff as failure.
- Do not hand-edit lockfiles when regeneration is available.
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 · 34 lines · 29 tokens per session scan A 305d844e1097
roll-resolve is a skill published in the GitHub repository sumimakito/roll (2 stars, last pushed 4mo ago), licensed MIT. It adds 29 tokens to every session and 368 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
pr
Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.
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.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…