agentmods.dev

chief-rule

chief-rule is a skill for Claude Code from thaitype/chief. It costs 94 tokens per session (1,703 once invoked), scanned A, original, MIT.

A guided way to write one project rule into the .chief/rules folder. It asks about the rule, why it matters, when it applies, and examples.

In plain words
What is it for?
Use it to record coding standards, agreements, goals, or other rules for future work. It can also create the rules-folder structure for later use.
Why use it?
It helps turn an unwritten expectation into a clear, reusable project instruction.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions AGENTS.md.

Part of the chief-skills plugin — 15 skills shipped together

not rated 68repo +2 1mo ago A scan SkillSpector: pass 94 tokens original MIT

Good fit Use it to record coding standards, agreements, goals, or other rules for future work. It can also create the rules-folder structure for later use.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/thaitype/chief/chief-rule
View source ↗ thaitype/chief
Install

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.

Any agent
npx skills add thaitype/chief --skill chief-rule
Clone the repo
git clone --depth 1 https://github.com/thaitype/chief

Made for: Claude Code.

Or install chief-skills, the plugin that ships this one along with the rest of its 15 skills.

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 chief-rule

README.md
[![agentmods](https://agentmods.dev/badge/skills/thaitype/chief/chief-rule/github.svg)](https://agentmods.dev/skills/thaitype/chief/chief-rule)
Your own site
<a href="https://agentmods.dev/skills/thaitype/chief/chief-rule"><img src="https://agentmods.dev/badge/skills/thaitype/chief/chief-rule/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 chief-rule

Your own site · 80×15
<a href="https://agentmods.dev/skills/thaitype/chief/chief-rule"><img src="https://agentmods.dev/badge/skills/thaitype/chief/chief-rule.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 94 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,703 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original 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.00094 $0.01703
Opus 5.5 $0.00038 $0.00681
Sonnet 5.5 $0.00019 $0.00341
Haiku 4.5 $0.00009 $0.00170

Measured 2mo ago against content hash 686b0f7a94fb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

chief-rule 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 2mo 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.

skills/chief/chief-rule/SKILL.md · 139 lines

How it starts

The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are helping the user capture a single rule into .chief/_rules/. This is the proactive counterpart to /chief-retro — use it whenever the user has a rule in mind and wants to write it down now.

One invocation = one rule (path 2) or scaffolding only (path 1). Re-run for more.

Steps

1. Pre-flight

Just inspect — do NOT create anything yet. Note for later use:

  • whether .chief/ exists
  • whether .chief/_rules/ exists
  • whether .chief/_rules/README.md exists

Scaffolding (creating .chief/, .chief/_rules/, the README) happens at the END of the chosen path, not now. If the user bails out, we leave the filesystem untouched.

2. Pre-interview fork

Ask the user, with exactly two options:

Pick one:

  1. Scaffold .chief/_rules/ only (I'll write rules manually later, or use /chief-retro after work)
  2. Interview me — write a rule now

If 1 → run the scaffold routine below, then stop. If 2 → continue to step 3. (Scaffolding happens later, in step 7, alongside the rule write.)

Scaffold routine (used by path 1, and by path 7 when _rules/ is missing)

  1. Create .chief/ if missing.

  2. Create .chief/_rules/ if missing.

  3. Write .chief/_rules/README.md if missing, with this content:

    # .chief/_rules/

Global rules that govern this project's autonomous AI work. Lower priority than `AGENTS.md`, higher than milestone goals.

## Categories

- `_standard/` — Coding standards, architecture constraints
- `_contract/` — Data models, API contracts, schemas
- `_goal/` — High-level goals (shared across milestones)
- `_verification/` — Test commands, build requirements, definition of done

Subfolders are created **lazily** — on first rule in that category. Empty subfolders are not required.

Use `/chief-rule` to add rules proactively, or `/chief-retro` to capture them after a milestone retrospective.

  4. Do NOT create the four category subfolders. They remain lazy until the first rule lands in each.

Read the full file on GitHub · 139 lines

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. 2mo ago First seen · 139 lines · 94 tokens per session scan A 686b0f7a94fb

Subscribe to this mod's changes

chief-rule is a skill published in the GitHub repository thaitype/chief (68 stars, last pushed 1mo ago), licensed MIT. It adds 94 tokens to every session and 1,703 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-30.

PlanningWriting and docs
Related

chief-rule compared with skills from other repositories

chief-rule next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
chief-rulethaitype/chiefSkill681mo agoMITA94Claude Code
imagegenopenai/codexSkill134ktodayApache-2.0A113Codex
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79kyesterdayMITA200Claude Code, Codex
playwright-climicrosoft/playwrightSkill100kyesterdayApache-2.0A19Claude Code
browser-automationopenclaw/openclawSkill394ktodayMITA36Claude Code
systematic-debuggingobra/superpowersSkill314k4d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143kyesterdayMITA95Claude Code