agent-rules-skill-author

A guide for creating and maintaining agent instructions and skill packages in a repository. It covers files such as AGENTS.md, shared rules, project guidance, skills, metadata, and validators.

In plain words
What is it for?
Use it to create, review, rename, delete, or edit skills, agent rules, manifests, validators, shared guidance, project guidance, and related README documentation.
Why use it?
It helps keep instructions in the right place and prevents project-specific rules from leaking into general guidance. It also provides boundaries for documentation and skill-maintenance work.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/ytvee-dev/webdev-agent-kit/agent-rules-skill-author
Any agent
npx skills add ytvee-dev/webdev-agent-kit --skill agent-rules-skill-author
Clone the repo
git clone --depth 1 https://github.com/ytvee-dev/webdev-agent-kit

Made for: Claude Code, Codex.

Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,731 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00045 $0.01731
Opus 5 $0.00023 $0.00865
Sonnet 5 $0.00009 $0.00346
Haiku 4.5 $0.00005 $0.00173

Measured 2d ago against content hash 8f3d1abc88e9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

agent-rules-skill-author 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 2d ago.

The scan reads SKILL.md. This mod also ships 4 executable files (scripts/generate_openai_yaml.py, scripts/init_agent_skill.py, scripts/skill_common.py, …), 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.

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/agent-rules-skill-author/SKILL.md · 150 lines

How it starts

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

Agent Rules And Skill Author

Purpose

Create or revise repo-local agent rules and .agents-compatible skill packages without leaking project-specific instructions into the wrong layer.

When To Use

  • The user asks to create, evaluate, rename, delete, or edit skills.
  • The user asks to change AGENTS.md, manifests, validators, common/**, project/**, or skills/**.
  • The user explicitly asks for user-facing README documentation changes.
  • The screenshot-to-frontend pipeline rules, tool contracts, or skill routing need maintenance.

When Not To Use

  • The user asks to write a design implementation spec from screenshots. Use design-screenshot-spec.
  • The user asks to implement a frontend layout from a spec. Use frontend-layout-implementer.
  • The user asks to visually verify rendered UI. Use frontend-visual-qa.
  • The user asks to adapt a new project in Plan Mode. Use project-onboarding-adapter.

Required Context

  1. Read AGENTS.md.
  2. Confirm the classified task is skill-documentation-refactor, documentation, or another .agents rule-maintenance task.
  3. Read common/documentation-maintenance.md.
  4. Read affected common/**, skills/**, project/**, manifests, validators, templates, examples, and root pointer files for the requested change.
  5. Apply common/readme-policy.md: read targeted README sections when the request concerns README, public setup guidance, or docs/implementation drift; verify technical claims through higher evidence.
  6. Read relevant references from this skill only when their topic is in scope.
  7. Read current OpenAI Codex docs when native skill behavior, AGENTS.md, MCP, plugins, or agents/openai.yaml behavior may have changed.

Tool Contract

  • Use filesystem reads and targeted search for local bundle facts.
  • Activate openai_platform_docs when current OpenAI or Codex behavior affects the change; follow common/codex-official-docs-policy.md.
  • Use context7 and mdn only when authoring rules depend on current framework or web platform behavior.
  • Do not use Figma MCP for this bundle.

Read the full file on GitHub · 150 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. 2d ago First seen · 150 lines · 45 tokens per session scan A 8f3d1abc88e9

Subscribe to this mod's changes

agent-rules-skill-author is a skill published in the GitHub repository ytvee-dev/webdev-agent-kit (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 45 tokens to every session and 1,731 once invoked, about $0.0002 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-08-31.

Related

Other skills, from other repositories

design-dna

Extract, define, and apply design DNA across three dimensions: design system (tokens), design style (qualitative feel), and visual effects (Canvas, WebGL, 3D, particles, shaders, scroll effects, etc.). Use this skill when: (1) a user wants to see the full 3-dimension design structure/schema, (2) a user provides…

zanwei/design-dna · 192 tokens

playwright-cli

Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…

testdino-hq/playwright-skill · 64 tokens

shipping-reproducible-results

Package completed data analysis and ML work so an independent recipient can reproduce the claimed results, verify artifact lineage, and operate the handoff within its stated scope. Use when finalizing a project, study, model package, or review bundle; not for deploying to a live system.

aiopshwang/data-analysis-ml-agent-skills · 62 tokens

actions-reusable-workflows

Wire a repository to the bitwise-media-group/github-workflows reusable workflows — thin, SHA-pinned caller workflows for CI, security (CodeQL) scanning, release (release-please/GoReleaser/Zensical docs), the signature-preserving fast-forward /merge + merge-review-ack + merge-notice flows, and add-to-project — plus the…

bitwise-media-group/skills · 172 tokens

go-style

Modern Go code style for stdlib-first programs — error wrapping with %w, sentinel errors, structured logging with log/slog, context threading, consumer-defined interfaces, nil-safe constructors, net/http servers with method-pattern routing, flag/env configuration for services, and cobra commands with viper…

bitwise-media-group/skills · 151 tokens

workflow-skill-evals

Write the evolve evaluation suite for an agent skill: its triggers (triggers.json — Tier 1 activation tests) and behavioral evals (evals.json — Tier 2 task tests), under evals/ /. Use when asked to generate, write, author, scaffold, or balance an eval suite, evals, or triggers for a skill; to create or edit a…

bitwise-media-group/skills · 201 tokens