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 oxidian/cc-plugins --skill open-mrgit clone --depth 1 https://github.com/oxidian/cc-pluginsWrote 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/oxidian/cc-plugins/open-mr)<a href="https://agentmods.dev/skills/oxidian/cc-plugins/open-mr"><img src="https://agentmods.dev/badge/skills/oxidian/cc-plugins/open-mr/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/oxidian/cc-plugins/open-mr"><img src="https://agentmods.dev/badge/skills/oxidian/cc-plugins/open-mr.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.00013 | $0.00339 |
| Opus 5.5 | $0.00005 | $0.00136 |
| Sonnet 5.5 | $0.00003 | $0.00068 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade A, and why
open-mr 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 1mo 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.
This is a copy
88% identical to open-pr — 18 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Context
First, run these commands and review their output:
- Current git status:
git status --porcelain - Current branch:
git branch --show-current - Recent commits:
git log --oneline -10
You usually already know what changed in this session. If you are unsure what the changes are, run git diff HEAD (or a targeted git diff HEAD -- <file>) before committing.
Commit and MR style
- Use a short commit/MR title (one line, imperative mood) that describes WHAT changed - never meta-messages like "Address review feedback" or "Fix MR comments"
- The commit/MR body should usually be blank - the code should speak for itself
- ONLY add a body to explain NON-OBVIOUS changes that aren't clear from the code
- AVOID summarising or describing what the code does in the MR body - that's redundant. AVOID including test plans.
- If we were working on a known GitLab issue, include "Closes #ISSUE" in the MR body
- See recent commits for examples (ignore bot commits)
Your task
Based on the above changes:
- Create a new branch if on main (do NOT add timestamps to branch names)
- Create a single commit with an appropriate message
- Push the branch to origin
- Create a merge request using
glab mr create. Do not use the--filloption. - Execute each step as a separate command. Do NOT chain commands with && or ;.
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.
- 1mo ago First seen · 33 lines · 13 tokens per session scan A db7669d266b9
open-mr is a skill published in the GitHub repository oxidian/cc-plugins (11 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 13 tokens to every session and 339 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to open-pr, differing in 18 lines, and is treated as a copy.
Other skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
review-delta
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
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.
git-pr-workflows-git-workflow
Guide changes through code checks, testing, commits, and pull request preparation. Use when coordinating a complete Git workflow and verifying readiness for collaboration.