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-feedbackgit 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-feedback)<a href="https://agentmods.dev/skills/tomosia-vietnam/open-pr/open-pr-feedback"><img src="https://agentmods.dev/badge/skills/tomosia-vietnam/open-pr/open-pr-feedback/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-feedback"><img src="https://agentmods.dev/badge/skills/tomosia-vietnam/open-pr/open-pr-feedback.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.00044 | $0.00191 |
| Opus 5.5 | $0.00018 | $0.00076 |
| Sonnet 5.5 | $0.00009 | $0.00038 |
| Haiku 4.5 | $0.00004 | $0.00019 |
Grade A, and why
open-pr-feedback 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
Read../../adapters/root.md(relative to this file) →ROOT+ this platform's tool names.ReadROOT/commands/feedback.md→ obey VERBATIM, every step, in order. Arguments handed to this skill are that file'sARGUMENTS.
This one posts in public. What may and may not go into the text, and when the user must approve it, is stated in that file — nothing is sent before they answer.
FORBIDDEN: summarizing, reordering or skipping a step; sending 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.
- 2mo ago First seen · 15 lines · 44 tokens per session scan A f33760aace8a
open-pr-feedback is a skill published in the GitHub repository TOMOSIA-VIETNAM/open-pr (44 stars, last pushed yesterday), licensed MIT. It adds 44 tokens to every session and 191 once invoked, about $0.0002 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-30.
Other skills, from other repositories
project-onboarding
Standard procedure for onboarding new software projects: Feature analysis, code quality review, onboarding checklist, and task creation.
codebase-migration-batches
Use when a wide refactor or migration is too large to ship as one change — API renames across many files, framework or config migrations, or mechanical codemod-backed refactors that need reviewable batches.
pm-tech-spec-review
Review an engineering technical spec through a PM lens — does it cover every PRD requirement, does it preserve user/UX intent, does it quietly add or drop scope, what are the product risks, what's missing for launch. Produces a priority-tagged findings list + clarifying questions for engineering. Use after eng drafts…
ai-maintainer-copilot
Use when maintaining open-source projects with AI assistance: issue triage, pull request review, release notes, maintainer automation, Codex for OSS application evidence, and privacy or safety guardrails for AI-assisted workflows.
triage
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
docs-governance
Route broad documentation-governance requests to existing ECC skills and run an opt-in, read-only audit of mapped documentation roles, links, ADR indexes, and evidence references. Use when a user asks for documentation governance, project-knowledge organization, documentation integrity, or a deterministic docs audit…