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 agentmods add skills/jeremydev87/codingbuddy/rule-authoringnpx skills add JeremyDev87/codingbuddy --skill rule-authoringgit clone --depth 1 https://github.com/JeremyDev87/codingbuddyWrote 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/jeremydev87/codingbuddy/rule-authoring)<a href="https://agentmods.dev/skills/jeremydev87/codingbuddy/rule-authoring"><img src="https://agentmods.dev/badge/skills/jeremydev87/codingbuddy/rule-authoring.svg" alt="Measured on agentmods" 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 | $0.00053 | $0.01792 |
| Opus 5 | $0.00026 | $0.00896 |
| Sonnet 5 | $0.00011 | $0.00358 |
| Haiku 4.5 | $0.00005 | $0.00179 |
Grade A, and why
rule-authoring 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 today.
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 — 279 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rule Authoring
Overview
AI coding rules are instructions that shape how AI assistants behave. Poorly written rules are ignored, misinterpreted, or cause inconsistent behavior across tools.
Core principle: Rules must be unambiguous, actionable, and testable. If an AI assistant can interpret a rule two different ways, it will choose the wrong one at the worst moment.
Iron Law:
EVERY RULE MUST HAVE A TESTABLE "DID IT WORK?" CRITERION
When to Use
- Writing new rules for
.ai-rules/rules/ - Updating existing rules that produce inconsistent behavior
- Adapting rules for a new AI tool (cursor, codex, q, kiro)
- Auditing rules for ambiguity or overlap
Rule Quality Criteria
A good rule is:
| Quality | Bad Example | Good Example |
|---|---|---|
| Specific | "Write good code" | "Functions must have a single return type" |
| Actionable | "Be careful with auth" | "All endpoints must check authentication before executing" |
| Testable | "Follow best practices" | "Test coverage must be ≥ 80% for new files" |
| Bounded | "Always use TypeScript" | "Use TypeScript strict mode in all .ts files" |
| Non-overlapping | Two rules about the same thing | One rule per concern |
Rule Structure
Core Rule Format
## [Rule Category]: [Rule Name]
**When:** [Trigger condition — when does this rule apply?]
**Do:** [Specific action to take]
**Don't:** [Specific anti-pattern to avoid]
**Example:**
\`\`\`typescript
// ✅ Good
function getUser(id: string): Promise<User>
// ❌ Bad
function getUser(id: any): any
\`\`\`
**Why:** [One-sentence rationale]
Rule File Structure
# [Category Name]
Brief description of what rules in this file govern.
## Rules
### Rule 1: [Name]
...
### Rule 2: [Name]
...
## Rationale
Why these rules exist for this project.
## Exceptions
Cases where these rules do not apply (keep this list short).
Writing Process
Phase 1: Identify the Rule Need
What ships with it
2 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.
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.
- today First seen · 279 lines · 53 tokens per session scan A 34de20e706ef
rule-authoring is a skill published in the GitHub repository JeremyDev87/codingbuddy (31 stars, last pushed 4mo ago), licensed MIT. It adds 53 tokens to every session and 1,792 once invoked, about $0.0003 per session on Opus 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-03.
Other skills, from other repositories
ring:searching-code
Forensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use…
ring:exploring-codebases
Exploring a codebase across phases: scopes the target, detects architecture, components, and layers, deep-dives each discovered perspective, then synthesizes findings into actionable guidance with file:line evidence. Use to understand how a feature or system works before planning changes, or to orient on an unfamiliar…
ring:auditing-dependency-security
Auditing a dependency for supply-chain risk before install (pip/npm/go/cargo): checks typosquatting, maintainer/age risk, vulnerability DBs (OSV, GHSA, Socket), and lockfile hash pinning, then emits a risk score and approve/conditional/escalate/block decision. Use when adding or updating a dependency, reviewing a…
ring:checking-frontend-quality
Checking frontend quality against changed UI via ring:qa-frontend in accessibility, visual, e2e, or performance mode and aggregating pass/fail verdicts. Use when a frontend change needs standalone a11y, visual-snapshot, Playwright e2e, or Lighthouse/Core-Web-Vitals validation outside the dev cycle. Skip for…
bzdesignprompt
为前端或网页设计任务选择并下载合适的 DESIGN.md 模板。当用户需要网页设计模板、UI 风格参考、设计系统、落地页或前端界面设计时，浏览长亭百智云 UI 设计模板库，根据产品场景和视觉偏好匹配模板，并将完整 DESIGN.md 保存到项目中。.
verify-quality
Verify code quality including naming conventions, organization, documentation, and general best practices. Use when asked to "verify quality", "check code quality", or "review code organization".