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 TOMOSIA-VIETNAM/open-pr --skill open-pr-cleangit clone --depth 1 https://github.com/TOMOSIA-VIETNAM/open-prWrote 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/tomosia-vietnam/open-pr/open-pr-clean)<a href="https://agentmods.dev/skills/tomosia-vietnam/open-pr/open-pr-clean"><img src="https://agentmods.dev/badge/skills/tomosia-vietnam/open-pr/open-pr-clean/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/tomosia-vietnam/open-pr/open-pr-clean"><img src="https://agentmods.dev/badge/skills/tomosia-vietnam/open-pr/open-pr-clean.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00042 | $0.00195 |
| Opus 5 | $0.00021 | $0.00097 |
| Sonnet 5 | $0.00008 | $0.00039 |
| Haiku 4.5 | $0.00004 | $0.00019 |
Grade A, and why
open-pr-clean 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 11d 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
Read../../adapters/root.md(relative to this file) →ROOT+ this platform's tool names.ReadROOT/commands/clean.md→ obey VERBATIM, every step, in order. Arguments handed to this skill are that file'sUsage:block.
This one deletes directories. What may be deleted, and what is unrecoverable if you touch it, is stated in that file — read it before listing anything, and never delete before the user answers.
FORBIDDEN: summarizing, reordering or skipping a step; deleting from what this file says; treating a tool you lack as a step you may drop.
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.
- 11d ago First seen · 15 lines · 42 tokens per session scan A 1f348d4212d0
open-pr-clean is a skill published in the GitHub repository TOMOSIA-VIETNAM/open-pr (42 stars, last pushed 6d ago), licensed MIT. It adds 42 tokens to every session and 195 once invoked, about $0.0002 per session on Opus 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
openclaw-github-dedupe
Investigate a cluster of GitHub issues and PRs, determine canonical candidates, post duplicate/related status, preserve contributor credit, and execute cleanup actions. Supports autonomous mode for provided-link-only closeout, merge/fix follow-through, changelog, and post-merge issue/PR cleanup.
pr-creator
Creates or updates GitHub PRs with house-style titles and bodies, issue linking, repository templates, and draft state. Use when asked to "create a PR", "rewrite the PR description", or "polish this PR". For code fixes use tidy; for CI and review threads use pr-babysitter; for npm releases use autoship.
github-commenting
How to post clean, rich, deduplicated GitHub PR review comments — suggestion blocks, multi-line anchors, markers, formatting rules. Load before posting or fixing any PR comment.
openclaw-pr-batch-sweep
Select, review, repair, validate, and land batches of up to 20 low-risk OpenClaw contributor pull requests using Vincent's maintainer preferences and bounded sub-agent lanes. Use for "next 20", broad contributor PR sweeps, merge-candidate mining, or continued PR-batch work where drafts, maintainer work, trivial…
pr-review
Use when opening, reviewing, or merging a pull request. Covers pre-PR checks (linting, tests, branch naming), PR description requirements, and post-merge cleanup. Not for code review commentary or architecture decisions — use the relevant role guidelines for those.
cmd_code_review
Code review — local uncommitted changes or GitHub PR (pass PR number/URL for PR mode).