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.
/plugin marketplace add tufantunc/review-pronpx agentmods add plugins/tufantunc/review-pro/coregit clone --depth 1 https://github.com/tufantunc/review-proGrade A, and why
review-pro 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": "review-pro",
"version": "1.2.0",
"description": "Tiered AI code-review: triage -> relevant specialist reviewers -> synthesis. Built to catch what AI-written code actually ships with — hallucinated APIs, over-engineering, ignored conventions, needless dependencies. Invoke the `review-pro` skill on a branch or PR.",
"author": {
"name": "tufantunc",
"url": "https://github.com/tufantunc"
},
"homepage": "https://tufantunc.github.io/review-pro/",
"repository": "https://github.com/tufantunc/review-pro",
"license": "MIT",
"keywords": [
"code-review",
"ai-code-review",
"security",
"code-quality",
"subagents",
"skills"
]
}
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 · 21 lines scan A 53ed6d4aa193
review-pro is a plugin published in the GitHub repository tufantunc/review-pro (4 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-08-31.
Other plugins, from other repositories
logic-lens-marketplace
Plugin marketplace listing 1 plugin: logic-lens.
logic-lens
Logic-first code review using semi-formal execution tracing. Surfaces behavioral bugs, semantic errors, and runtime failures that linters miss.
stometa
Plugin marketplace listing 1 plugin: harness-engineering-skills.
harness-engineering-skills
Two Claude Code engineering skills bundled as one plugin: review-loop (cross-LLM iterative code review with Codex or Gemini as peer) and harness (cybernetics-based Planner→Generator→Evaluator→Retro orchestration for complex tasks).
code-audit-protocol
Plugin marketplace listing 1 plugin: audit-protocol.
audit-protocol
Audits a code change against a 54-phase failure taxonomy and reports what it did not check, not just what it found. Domain overlays run first and force critical-path treatment.