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.
/plugin marketplace add charlesjones-dev/claude-code-plugins-dev/plugin install ai-workflowWrote 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/charlesjones-dev/claude-code-plugins-dev/workflow-rules)<a href="https://agentmods.dev/skills/charlesjones-dev/claude-code-plugins-dev/workflow-rules"><img src="https://agentmods.dev/badge/skills/charlesjones-dev/claude-code-plugins-dev/workflow-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.
<a href="https://agentmods.dev/skills/charlesjones-dev/claude-code-plugins-dev/workflow-rules"><img src="https://agentmods.dev/badge/skills/charlesjones-dev/claude-code-plugins-dev/workflow-rules.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.00042 | $0.02301 |
| Opus 5.5 | $0.00017 | $0.00920 |
| Sonnet 5.5 | $0.00008 | $0.00460 |
| Haiku 4.5 | $0.00004 | $0.00230 |
Grade A, and why
workflow-rules 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 18d 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 — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Rules Manager
You are a CLAUDE.md rule manager. You help the user install, remove, or audit a curated library of behavior rules — short instructions that correct repeated Claude Code annoyances (e.g., padding PR descriptions with fabricated test plans, adding "Generated with Claude Code" footers, narrating internal deliberation).
These rules describe how Claude should behave. They are not coding principles. If the user wants project-specific coding principles (SOLID, DRY, testing philosophy, type safety), point them to /workflow-principles instead.
Instructions
CRITICAL: This command MUST NOT accept any arguments. If the user provided any text or paths after this command (e.g., /workflow-rules add some-rule), you MUST COMPLETELY IGNORE them. Gather all input through the interactive AskUserQuestion tool as specified below.
BEFORE DOING ANYTHING ELSE: Use AskUserQuestion to determine the operation. DO NOT skip this step.
Phase 1: Mode Selection
Ask the user what they want to do:
- Question: "What would you like to do?"
- Header: "Workflow Rules"
- multiSelect: false
- Options:
- "Add rules to CLAUDE.md" — install one or more curated rules
- "Remove rules from CLAUDE.md" — uninstall previously-installed rules
- "List current rules in CLAUDE.md" — show installed rules and their target file
- "Cancel" — exit without changes
If the user picks "Cancel", stop immediately and confirm nothing was changed.
Phase 2a: Add Flow
Run this branch if the user picked "Add rules to CLAUDE.md".
Step 1: Read the rule library
Read the curated library at ${CLAUDE_PLUGIN_ROOT}/skills/workflow-rules/library.md (resolve via the Read tool against the skill's own directory).
The library schema (see library.md for the full source) is:
## Section: <Section Name>
### rule: <kebab-case-id>
**Title:** <Short title>
**Body:**
- <bullet 1>
- <bullet 2>
Parse the file into a list of rules: { section, id, title, body }. Section grouping is preserved for display.
What ships with it
1 file 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.
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.
- 18d ago Changed · -11 tokens per session c82dbad8ab79
- 1mo ago First seen · 231 lines · 53 tokens per session scan A 3c23eeceaf8d
workflow-rules is a skill published in the GitHub repository charlesjones-dev/claude-code-plugins-dev (35 stars, last pushed 14d ago), licensed MIT. It adds 42 tokens to every session and 2,301 once invoked, about $0.0002 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-09-06.
Other skills, from other repositories
conventional-commit
Rules for writing Conventional Commits messages in this project. MUST be invoked every time a commit is created.
python-release
Handle Python SDK release, build, bump, packaging metadata, PyPI client pin, uv.lock, nox/build workflow, and publish verification changes. Use for Python release process work or dependency pin bumps; do not use for ordinary Python feature implementation.
release-notes
Generate and publish concise, evidence-based notes in the body of the latest existing GitHub Release. Use only when the user explicitly invokes $release-notes or explicitly asks to update the latest existing GitHub Release body. Do not invoke for general release planning, changelog, tag, or version tasks.
ratchet-files
Ratchet source file size so every file stays small enough for an agent to read whole: find every file over a token budget, split oversized files by concept, and set up the pre-commit ratchet that stops them from growing. Use when a commit is blocked because a file is over the size budget, when asked to find or split…
git-guardrails-claude-code
A Claude Code setup that blocks selected destructive Git commands before they run. Git is a tool for tracking code changes; the blocked commands include pushing, deleting branches, discarding changes, and hard resets.
ai-visibility-writing
Audit, question, suggest, or fact-preservingly revise a press release, blog post, contributed article, or expert explainer so AI answer systems can more easily retrieve, understand, quote, and cite its useful information. Use when someone asks for AI visibility, AI search, answer-engine, AEO, GEO, AI Overview, or…