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 orin-dx/agent-plugins --skill post-reviewgit clone --depth 1 https://github.com/orin-dx/agent-pluginsWrote 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/orin-dx/agent-plugins/post-review)<a href="https://agentmods.dev/skills/orin-dx/agent-plugins/post-review"><img src="https://agentmods.dev/badge/skills/orin-dx/agent-plugins/post-review.svg" alt="Measured on agentmods" 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.00041 | $0.00278 |
| Opus 5 | $0.00020 | $0.00139 |
| Sonnet 5 | $0.00008 | $0.00056 |
| Haiku 4.5 | $0.00004 | $0.00028 |
Grade A, and why
post-review 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 today.
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
Deliver approved review content
This skill performs a visible external action only. It does not critique code, determine whether feedback is correct, or rewrite the user's prepared response.
Required input
- Exact comment or review body.
- Precise repository and pull-request target.
- Thread identifier when replying to or resolving a specific thread.
- Intended operation: comment, review submission, reply, or resolve.
Workflow
- Verify that the target exists and that the requested operation matches the supplied identifiers.
- Show the exact text, target, and operation verbatim.
- Ask for explicit confirmation.
- Perform only the confirmed external action and report its resulting URL or identifier.
Safety
- Never post, submit, or resolve a thread from a summary, inferred intent, or prior confirmation for different text.
- Do not combine several comments into one action unless the user sees and confirms every target and body.
- If the text needs authoring or substantive review, route that work to the user or the relevant review workflow before returning here.
Team use
Do not request an agent team. This is a narrow, externally visible delivery step.
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.
- today Changed · +7 lines · -83 tokens per session 05d4e1c780c5
- 7d ago First seen · 26 lines · 124 tokens per session scan A d925aba910d7
post-review is a skill published in the GitHub repository orin-dx/agent-plugins (1 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 278 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-31.
Other skills, from other repositories
max
Cleans up and improves existing code without changing behavior.
dorodango
Polishes working code through successive quality passes in fresh subagents. Use after tests pass when code needs multi-dimension refinement before release.
git-pr-workflows-git-workflow
Orchestrate a comprehensive git workflow from code review through PR creation, leveraging specialized agents for quality assurance, testing, and deployment readiness. This workflow implements modern g.
code-reviewer
Elite code review expert specializing in modern AI-powered code analysis, security vulnerabilities, performance optimization, and production reliability. Masters static analysis tools, security scanning, and configuration review with 2024/2025 best practices. Use PROACTIVELY for code quality assurance.
ring:exploring-codebases
Exploring a codebase across phases: scopes the target, detects architecture, components, and layers, deep-dives each discovered perspective, then synthesizes findings into actionable guidance with file:line evidence. Use to understand how a feature or system works before planning changes, or to orient on an unfamiliar…
ring:searching-code
Forensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use…