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 tomoking2004/claude-plugins --skill codegit clone --depth 1 https://github.com/tomoking2004/claude-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/tomoking2004/claude-plugins/code)<a href="https://agentmods.dev/skills/tomoking2004/claude-plugins/code"><img src="https://agentmods.dev/badge/skills/tomoking2004/claude-plugins/code/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/tomoking2004/claude-plugins/code"><img src="https://agentmods.dev/badge/skills/tomoking2004/claude-plugins/code.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.00100 | $0.00446 |
| Opus 5.5 | $0.00040 | $0.00178 |
| Sonnet 5.5 | $0.00020 | $0.00089 |
| Haiku 4.5 | $0.00010 | $0.00045 |
Grade A, and why
code 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 1mo 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.
What it actually says
対象：指定された範囲のコード；無指定ならプロジェクト全コード（生成物のみ除く；.gitignore 対象も走査し，私的なメモ等は変更前に問う）．
まず BEAUTY.md を読み，美の6条と走査の規律に従う．
媒体の正典
- Python：PEP 8・PEP 20・PEP 257．公開 API は型ヒントと Docstring を持つ．
- その他の言語：その言語の公式スタイルガイド；無ければ既存ファイルの多数派．
固有の走査
- 名前鎖：公開名・改名は定義→呼び出し→引数→直列化キー→テンプレート→Docstring まで追跡し，全箇所を一致させる．
- 識別子族：同義語群・動詞族・接頭辞/接尾辞の規約をコード全域で列挙し，揺れを潰す．
制約
公開挙動は保つ——変更のたびにテスト・実行で確かめ，バグ修正で変わるなら明示する．git は読み込みのみ．判断の割れる箇所は推測せず問う．
失敗時
/heal:skill を呼ぶ．
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.
- 1mo ago First seen · 27 lines · 100 tokens per session scan A 7c4497da41c3
code is a skill published in the GitHub repository tomoking2004/claude-plugins (3 stars, last pushed 2mo ago), licensed MIT. It adds 100 tokens to every session and 446 once invoked, about $0.0004 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-31.
Other skills, from other repositories
phpunit-test-team-reviewing
Use this skill when the user asks for a team-based, consensus, multi-reviewer, or red-team review of Shopware PHPUnit tests — trigger phrases like "team review these tests", "consensus review the tests in PR.
phpunit-test-reconciling
Internal sub-skill. Do not auto-activate. Use only when explicitly invoked by name by another skill or agent.
audit-comment-residue
Read-only classifier that flags residue in code comments: history narration, plan or session references, conversational asides, ticket or PR back-references, origin notes, and workarounds with no link or removal condition. Use when asked to 'audit code comments' or report which comments only make sense with the chat…
issue-analyzing
Use this skill when the user asks to analyze a specific GitHub issue, understand what area of code an issue affects, assess an issue's scope, or research the code context around an issue — example triggers like "analyze issue.
pr-analyzing
Use this skill when the user asks to analyze a specific GitHub pull request, review a PR's architectural impact, assess what changed in a PR and why it matters, or research the code relationships affected by a PR — example triggers like "analyze PR.
improve
Codebase scan for module-level friction (shallow modules, seam leaks, locality gaps): an HTML candidate report, then a Design-It-Twice interview on the chosen one. Use when 'improve architecture', 'find deepening opportunities', 'shallow modules', 'design it twice', 'compare alternative interfaces', 'make code more…