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 agentmods add skills/usk6666/yorishiro-proxy/code-reviewnpx skills add usk6666/yorishiro-proxy --skill code-reviewgit clone --depth 1 https://github.com/usk6666/yorishiro-proxyWrote 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/usk6666/yorishiro-proxy/code-review)<a href="https://agentmods.dev/skills/usk6666/yorishiro-proxy/code-review"><img src="https://agentmods.dev/badge/skills/usk6666/yorishiro-proxy/code-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 | $0.00017 | $0.00721 |
| Opus 5 | $0.00009 | $0.00360 |
| Sonnet 5 | $0.00003 | $0.00144 |
| Haiku 4.5 | $0.00002 | $0.00072 |
Grade A, and why
code-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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/code-review
A skill for conducting code quality reviews on Pull Requests.
Argument Patterns
/code-review <PR number>— Review the specified PR/code-review— Review the PR associated with the current branch
Steps
Step 1: Identify the PR
If an argument is provided:
- Use
<PR number>
If no argument is provided:
- Get the PR number for the current branch with
gh pr view --json number -q .number - If no PR exists, display an error message and exit
Step 2: Fetch PR Information
Fetch the following in parallel:
gh pr view <PR number> --json title,body,headRefName,baseRefName,number,url
gh pr diff <PR number> --name-only
- Record the PR title, branch name, and PR URL
- Get the list of changed files
Step 3: Fetch Issue Information (optional)
Extract a Linear Issue ID (USK-XX format) from the PR body.
If found, fetch the Issue description with mcp__linear-server__get_issue.
If not found, leave the Issue-related placeholders empty and continue.
Step 4: Build Product Context
yorishiro-proxy is a network proxy (MCP server) for AI agents.
Provides traffic interception, recording, and replay capabilities for vulnerability assessment.
Architecture: TCP Listener → Protocol Detection → Protocol Handler → Session Recording → MCP Tool
Step 5: Launch Code Review Agent
Read .claude/agents/code-reviewer.md with the Read tool and extract the code block inside the ## Prompt Body section.
Replace placeholders:
{{PR_NUMBER}}→ PR number{{PR_TITLE}}→ PR title{{ISSUE_ID}}→ Issue ID (or "N/A"){{ISSUE_DESCRIPTION}}→ Issue description (or "N/A"){{PRODUCT_CONTEXT}}→ Context built in Step 4{{CHANGED_FILES}}→ List of changed files
Launch with Task tool:
subagent_type:"general-purpose"isolation:"worktree"description:"Code review PR #<N>"prompt: Replaced prompt
Step 6: Report Results
Parse the sub-agent results and report to the user in the following format:
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.
- 5d ago First seen · 103 lines · 17 tokens per session scan A 639887e8b149
code-review is a skill published in the GitHub repository usk6666/yorishiro-proxy (16 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 721 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-08-30.
Other skills, from other repositories
screenshots
Advanced UI analysis and interaction through pixel-level reasoning to solve complex interaction problems, locate hard-to-find elements, verify visual states, and debug layout/rendering issues. Use as needed after UI Mapper inspection when advanced reasoning or non-standard views are required.
ida-reverse
IDA Pro reverse engineering assistance skill. Be sure to use this skill whenever the user mentions reverse engineering, decompilation, analyzing binary/PE/ELF/APK/DLL/SO files, cracking, finding passwords, vulnerability analysis, malware analysis, or firmware analysis, or needs to analyze exe/dll/so/elf/macho/sys…
patch-diff-exploit
N-day patch diffing to exploitation. Reverse-engineer the vulnerability from vendor-released patches, write a PoC, and turn it into a usable attack module. Use cases: a known CVE with a patch but no PoC, SRC/red team targeting assets that have not been updated in time, N-day weaponization, Patch Tuesday follow-up.…
reverse-engineering
Provides reverse engineering techniques. Use when the main job is to understand how a compiled, obfuscated, packed, or virtualized target works before exploiting or solving it, including binaries, APKs, WASM, firmware, custom VMs, bytecode, malware-like loaders, and anti-debug or anti-analysis logic. Do not use it…
ReverseOps-router
Routes reverse engineering, exploitation, penetration testing, malware, mobile, firmware, browser automation, documentation, and security tasks to the appropriate specialist skill. Use when a task spans modules or the correct ReverseOps entrypoint is unclear.
apk-reverse
Use when performing Android APK reverse engineering in a CLI environment. Applies to APK unpacking, Java decompilation, smali modification, repackaging, and Frida dynamic hooking, with on-demand switching to so/native analysis. Prefer locally installed jadx, apktool, frida, adb, ida-reverse, radare2.