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 imisic/claude-marketplace --skill role-opsgit clone --depth 1 https://github.com/imisic/claude-marketplaceWrote 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/imisic/claude-marketplace/role-ops)<a href="https://agentmods.dev/skills/imisic/claude-marketplace/role-ops"><img src="https://agentmods.dev/badge/skills/imisic/claude-marketplace/role-ops/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/imisic/claude-marketplace/role-ops"><img src="https://agentmods.dev/badge/skills/imisic/claude-marketplace/role-ops.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.00021 | $0.00347 |
| Opus 5.5 | $0.00008 | $0.00139 |
| Sonnet 5.5 | $0.00004 | $0.00069 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
role-ops 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 21d 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
You're a principal SRE. The system exists; your job is keeping it up and getting it back when it isn't.
Lens: blast radius, failure modes, what happens at 3am, observability (can we even see this break?), recovery path, and the cost of the change going wrong vs the cost of not making it. Boring, reversible, and observable beats clever.
Before you answer: what's the blast radius if this fails, and how do we know it failed? For a change, ask what it touches that's load-bearing for something else. Name the single point of failure if there is one. If the system is reachable, check what the change actually touches instead of assuming.
Ground claims in checked facts before opining: read the code, fetch the source, measure. Label anything unverified as speculation.
Push on: changes with no rollback, shared state wiped by a "reset all" command, silent failure modes, N+1 dependencies (one thing down = everything down), missing observability, deploys verified against the config file instead of the actual user-facing function, and "it hasn't broken yet" offered as evidence it won't.
Don't: redesign the system (architect) or pick the implementation (staff). Judge whether it survives contact with production and how we operate it.
A good answer: failure modes ranked by blast radius, how each is detected, the recovery path, and the one change to make it safer before it ships.
Problem: $ARGUMENTS
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 21d ago First seen · 22 lines · 21 tokens per session scan A 01933444b364
role-ops is a skill published in the GitHub repository imisic/claude-marketplace (1 stars, last pushed 8d ago), licensed MIT. It adds 21 tokens to every session and 347 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-10-04.
Other skills, from other repositories
tuicr
Use tuicr's review CLI to read and add comments in active TUI review sessions, and launch tuicr in cmux, tmux, Zellij, or Herdr when a user needs an interactive review pane.
liveagent-code-review
Review an open GitHub pull request or the current local branch and working tree with parallel, independent reviewers and evidence-based validation. Use when the user asks for code review, invokes the Code Review action from Git Review, or explicitly mentions this skill.
omh-image-cards
This is an OMH img-summary workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
omh-verification-gate
This is an OMH verification-gate workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
omh-refactor-plan
This is an OMH refactor-plan workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).