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.
git 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/plugins/tomosia-vietnam/open-pr/gemini-extension)<a href="https://agentmods.dev/plugins/tomosia-vietnam/open-pr/gemini-extension"><img src="https://agentmods.dev/badge/plugins/tomosia-vietnam/open-pr/gemini-extension.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
open-pr 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 yesterday.
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
{
"name": "open-pr",
"version": "1.4.3",
"description": "Review pull requests on GitHub, GitLab and Bitbucket across many stacks, learning each repo's own conventions over time and posting one review through that vendor's own CLI or REST API."
}
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.
- yesterday First seen · 6 lines scan A 71c4697dccb4
open-pr is a plugin published in the GitHub repository TOMOSIA-VIETNAM/open-pr (42 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-06.
Other plugins, from other repositories
technical-deslop
Clean branch/staged diffs by removing AI-style slop and restoring repo-consistent style without changing behavior.
opik-integrations-auditor
Audit, compare, and document Opik integrations across Python, TypeScript, and backend OTEL/API surfaces with a repeatable evidence-first workflow.
ai-modernize
AI-powered codebase modernization assessment - Interactive audit and quick scan skills with an automated auditor agent to identify technical debt, anti-patterns, and quality issues from older AI-generated code.
code-review
Code review plugin.
open-pr
Pre-flight checks and PR creation workflow: run tests, open a PR, code review, and check CI.
hunch
A git-native reasoning graph of decisions, bugs, and invariants for your codebase — queried and enforced at reasoning time. Adds the hunch MCP tools plus /hunch:capture, /hunch:heal, /hunch:why, /hunch:fix, /hunch:fragile.