Borrowing it
Nothing to install: this file belongs to usk6666/yorishiro-proxy. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/usk6666/yorishiro-proxy/main/.claude/skills/implement-plugin/SKILL.mdgit 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/implement-plugin)<a href="https://agentmods.dev/skills/usk6666/yorishiro-proxy/implement-plugin"><img src="https://agentmods.dev/badge/skills/usk6666/yorishiro-proxy/implement-plugin/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/usk6666/yorishiro-proxy/implement-plugin"><img src="https://agentmods.dev/badge/skills/usk6666/yorishiro-proxy/implement-plugin.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.00022 | $0.04102 |
| Opus 5.5 | $0.00009 | $0.01641 |
| Sonnet 5.5 | $0.00004 | $0.00820 |
| Haiku 4.5 | $0.00002 | $0.00410 |
Grade A, and why
implement-plugin 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.
How it starts
The opening of the file, as written. The whole thing — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/implement-plugin
A workflow skill for creating Starlark plugins on the RFC-001 §9.3 plugin engine (internal/pluginv2/). Interactively select protocol/event/phase to generate a working scaffold.
Arguments
/implement-plugin— Create a plugin in interactive mode/implement-plugin <description>— Auto-generate a plugin from a description (e.g.,/implement-plugin Add X-Request-ID header to HTTP requests)
Steps
Phase 1: Requirements Clarification
If no description argument is given, interactively confirm:
- Purpose: What should the plugin do?
- Protocol: Target plugin protocol — one of
http,ws,grpc,grpc-web,sse,raw,tls,connection,socks5(the plugin protocol vocabulary; seeinternal/pluginv2/surface.go). - Event: Hook event under that protocol (e.g.
on_request,on_message,on_chunk). - Phase:
pre_pipeline(default — before Intercept/Transform) orpost_pipeline(after; right place for signing/last-mile mutation). Lifecycle / observation events (on_close,on_handshake,on_disconnect,socks5.on_connect, etc.) take nophase=argument — passing one is a load-time error. - Action: CONTINUE (mutate in place) / DROP (transaction-start only) / RESPOND (transaction-start request; on the response side
http.on_response/ws.on_upgradeon a 101 replace the upstream response,grpc.on_start/grpc-web.on_startend the RPC).
If a description argument is given, auto-determine from its content.
Phase 2: Context Collection
Read the following to understand the plugin API:
docs/rfc/plugin-migration.md— Direct migration table from legacy hook names to(protocol, event, phase)and the rationale.internal/pluginv2/surface.go— The 17-entry hook surface table. Authoritative for which (protocol, event) pairs exist and which actions each accepts.internal/pluginv2/convert.go— The Starlarkmsgdict shape per protocol (snake_case field names,*HeadersValueordered list,msg["raw"]first-class byte injection).internal/pluginv2/lifecycle.go— Dict shapes for lifecycle events (connection.on_connect,socks5.on_connect,tls.on_handshake,ws.on_close).internal/pluginv2/respond_action.go— Typedaction.RESPOND(...)/action.RESPOND_GRPC(...)builtin signatures.examples/plugins/— Existing sample plugins for each major protocol.
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 Changed · +7 lines b9e714e31a63
- 3d ago Changed d84c32999ab7
- 7d ago Changed 0a5688774e4f
- 8d ago Changed · +3 lines 1a55cc8ac694
- 11d ago Changed · +2 lines 0964a974ed40
- 1mo ago First seen · 151 lines · 22 tokens per session scan A 6fa28e576162
implement-plugin is a skill published in the GitHub repository usk6666/yorishiro-proxy (19 stars, last pushed yesterday), licensed Apache-2.0. It adds 22 tokens to every session and 4,102 once invoked, about $0.0001 per session on Opus 5.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.
firmware-pentest
Firmware / IoT pentest chain. Start from a .bin / .img blob and close the full loop: reverse → extract → emulate → exploit. Methodology follows the OWASP FSTM nine stages; the toolchain centers on binwalk v3, unblob, EMBA, Firmadyne, and AFL++. Use cases: router/camera/smart-home firmware audits, firmware update…
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.…
pentest-tools
Active penetration testing toolchain. Covers reconnaissance, port scanning, vulnerability scanning, web exploitation, SQL injection, directory brute-forcing, password cracking, and more. Exposes 20+ security tools to the AI agent via MCP servers (pentestMCP / mcp-security-hub). Trigger keywords: penetration testing…
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…