agentmods.dev

extract-rules

extract-rules is a skill for Claude Code from hiroro-work/claude-plugins. It costs 75 tokens per session (7,457 once invoked), scanned B, original, no licence file.

A skill that reads an existing codebase and writes its project-specific coding rules and subject knowledge as Markdown for coding agents.

In plain words
What is it for?
Use it when onboarding an existing project, documenting decisions from code reviews, or recording coding conventions after development sessions.
Why use it?
It helps when important conventions are scattered through the code and are not documented in one place.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter.

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /Users/alice/src/github.com/acme/widget.

Part of the extract-rules plugin — 1 skill shipped together

not rated 47repo changed 27d ago B scan 75 tokens no licence

Good fit Use it when onboarding an existing project, documenting decisions from code reviews, or recording coding conventions after development sessions.

Compare 6 skills from other repositories ↓
View source ↗ hiroro-work/claude-plugins
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add hiroro-work/claude-plugins
Claude Code
/plugin install extract-rules

Made for: Claude Code.

Or install extract-rules, the plugin that ships this one along with the rest of its 1 skill.

Wrote 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.

agentmods badge for extract-rules

README.md
[![agentmods](https://agentmods.dev/badge/skills/hiroro-work/claude-plugins/extract-rules/github.svg)](https://agentmods.dev/skills/hiroro-work/claude-plugins/extract-rules)
Your own site
<a href="https://agentmods.dev/skills/hiroro-work/claude-plugins/extract-rules"><img src="https://agentmods.dev/badge/skills/hiroro-work/claude-plugins/extract-rules/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.

agentmods 80×15 button for extract-rules

Your own site · 80×15
<a href="https://agentmods.dev/skills/hiroro-work/claude-plugins/extract-rules"><img src="https://agentmods.dev/badge/skills/hiroro-work/claude-plugins/extract-rules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 75 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 7,457 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00075 $0.07457
Opus 5.5 $0.00030 $0.02983
Sonnet 5.5 $0.00015 $0.01491
Haiku 4.5 $0.00007 $0.00746

Measured 27d ago against content hash 5d27a02b4a02, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

extract-rules scanned grade B with 1 finding 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 27d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/extract_session_messages.mjs), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

**`language` resolution:** skill config → Claude Code settings (`~/.claude/settings.json` `language` field) → default `ja`. Write the report's prose in plain words, one claim per sentence, with no figure of speech transl
plugins/dev-workflow-bundle/skills/extract-rules/SKILL.md · 486 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Files

What ships with it

16 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 27d ago Changed 5d27a02b4a02
  2. 1mo ago Changed · +18 lines 4766af4b78aa
  3. 1mo ago Changed · -244 lines b80ca930a903
  4. 1mo ago Changed b9552881c040
  5. 1mo ago First seen · 712 lines · 75 tokens per session scan B 19bd8f0c3d32

Subscribe to this mod's changes

extract-rules is a skill published in the GitHub repository hiroro-work/claude-plugins (47 stars, last pushed today), with no licence file. It adds 75 tokens to every session and 7,457 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Building agentsWriting and docs
Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…

vercel/next.js · 123 tokens