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 rp1-run/rp1 --skill pr-visualgit clone --depth 1 https://github.com/rp1-run/rp1Wrote 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/rp1-run/rp1/pr-visual)<a href="https://agentmods.dev/skills/rp1-run/rp1/pr-visual"><img src="https://agentmods.dev/badge/skills/rp1-run/rp1/pr-visual/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/rp1-run/rp1/pr-visual"><img src="https://agentmods.dev/badge/skills/rp1-run/rp1/pr-visual.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.00020 | $0.00698 |
| Opus 5 | $0.00010 | $0.00349 |
| Sonnet 5 | $0.00004 | $0.00140 |
| Haiku 4.5 | $0.00002 | $0.00070 |
Grade A, and why
pr-visual 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
Visual PR Analyzer
§ROLE: Standalone PR visualization orchestrator. Dispatches pr-visualizer, registers artifact.
STATE-MACHINE
stateDiagram-v2
[*] --> visualize
visualize --> [*] : done
On each phase transition, report via:
rp1 agent-tools emit \
--workflow pr-visual \
--type status_change \
--run-id {RUN_ID} \
--name "PR Visual: {PR_BRANCH}" \
--step {STATE} \
--data '{"status": "{running|completed}", "branch": "{PR_BRANCH}"}'
RUN_IDcomes from the generated Workflow Bootstrap section- Use the pre-resolved
projectRoot,kbRoot, andworkRootvalues from the generated Workflow Bootstrap section
§1 Visualize
Emit visualize running. Spawn the pr-visualizer agent:
{% dispatch_agent "rp1-dev:pr-visualizer" %} PR_BRANCH={PR_BRANCH}, BASE_BRANCH={BASE_BRANCH}, REVIEW_DEPTH={REVIEW_DEPTH}, FOCUS_AREAS={FOCUS_AREAS}, STANDALONE=true, KB_ROOT={kbRoot}, WORK_ROOT={workRoot} {% enddispatch_agent %}
Wait for completion. Extract the artifact path from agent output.
Register the artifact:
rp1 agent-tools emit \
--workflow pr-visual \
--type artifact_registered \
--run-id {RUN_ID} \
--step visualize \
--data '{"path": "{ARTIFACT_PATH}", "type": "pr-visual", "feature": "pr-visual", "storageRoot": "project"}'
Emit visualize completed. Output the artifact path.
{% include_shared "anti-loop.md" %}
File-specific constraints:
- Dispatch the visualizer agent exactly once, register exactly one artifact, then stop.
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 · 101 lines · 20 tokens per session scan A cc72ecd637e7
pr-visual is a skill published in the GitHub repository rp1-run/rp1 (38 stars, last pushed 2d ago), licensed Apache-2.0. It adds 20 tokens to every session and 698 once invoked, about $0.0001 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-09-07.
Other skills, from other repositories
review
Validate plans, execution, or PRs against wish criteria — returns SHIP / FIX-FIRST / BLOCKED with severity-tagged gaps.
fix
Dispatch fix subagent for FIX-FIRST gaps from review, re-review, then diagnose unresolved failures after 2 loops.
refactor-advisor
A code review helper that finds common design and maintenance problems in a codebase and suggests ways to restructure the code.
zh-code-reviewer
A Chinese-language code-review specialist that produces a structured review report. It examines coding style, possible bugs, performance, security, and design choices.
at-review
Review code changes for bugs, regressions, convention violations, and high-value cleanup opportunities. Use for diffs, commit ranges, hosted PR/MR URLs, branches, paths, staged changes, or working-tree changes.
architecture
Use when reviewing architecture in any codebase — module boundaries, stated design contracts, abstraction depth, error-handling design. Assess by default, apply changes on request; complexity is dependencies plus obscurity, and deep modules win.