guideline-writing

guideline-writing is a skill for Claude Code, Codex from event4u-app/agent-config. It costs 42 tokens per session (1,704 once invoked), scanned A, original, MIT.

A process for creating or substantially revising a guideline in a project's documentation. A guideline is reference material that other rules and skills can cite, rather than an instruction that triggers an action.

In plain words
What is it for?
Use it to write naming conventions and other project guidance, extract shared explanations from skills, or consolidate repeated reference material.
Why use it?
It helps keep reusable project knowledge in the right documentation form and prevents reference material from being mixed up with rules or workflows.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to write naming conventions and other project guidance, extract shared explanations from skills, or consolidate repeated reference material.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/event4u-app/agent-config/guideline-writing
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 event4u-app/agent-config --skill guideline-writing
Clone the repo
git clone --depth 1 https://github.com/event4u-app/agent-config

Made for: Claude Code, Codex.

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 guideline-writing

README.md
[![agentmods](https://agentmods.dev/badge/skills/event4u-app/agent-config/guideline-writing/github.svg)](https://agentmods.dev/skills/event4u-app/agent-config/guideline-writing)
Your own site
<a href="https://agentmods.dev/skills/event4u-app/agent-config/guideline-writing"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/guideline-writing/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 guideline-writing

Your own site · 80×15
<a href="https://agentmods.dev/skills/event4u-app/agent-config/guideline-writing"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/guideline-writing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,704 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.00042 $0.01704
Opus 5 $0.00021 $0.00852
Sonnet 5 $0.00008 $0.00341
Haiku 4.5 $0.00004 $0.00170

Measured 9d ago against content hash 25454d6f08f7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

guideline-writing 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 9d 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.

src/skills/guideline-writing/SKILL.md · 198 lines

How it starts

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

guideline-writing

When to use

  • Creating a new guideline in docs/guidelines/{topic}/{name}.md
  • Rewriting an existing guideline (not a typo fix)
  • Extracting reference material out of a bloated skill or rule
  • Consolidating repeated explanations from multiple skills

Do NOT use this skill when:

  • The content is a constraint ("never / always") → use rule-writing
  • The content is a triggered workflow → use skill-writing
  • The content is a user-invoked action → use command-writing

Guideline vs rule vs skill — critical test

Intent Artifact
"Here is knowledge skills and rules may cite" Guideline
"Agent must always / never do X" Rule
"When Y happens, run these steps" Skill

A guideline is reference material. It is never a trigger. It has no description used for routing — skills and rules link to it.

Procedure

0. Run the Drafting Protocol

Creating or materially rewriting a guideline must go through Understand → Research → Draft from the artifact-drafting-protocol rule.

  • Understand — which skills or rules will cite this guideline? If the answer is "none", the guideline has no home — stop.
  • Researchinspect docs/guidelines/ for overlap and grep src/ for pages that already cover the topic. Analyze 1–2 peer guidelines in the same topic folder for tone.
  • Draft — propose location (topic folder + filename) and outline. Only fill bodies once the outline is confirmed.

1. Pick the right topic folder

Folders under docs/guidelines/:

Folder Contents
agent-infra/ Cross-cutting agent-system knowledge (naming, size, output patterns)
php/ PHP-specific reference (patterns, services, jobs, resources)
e2e/ End-to-end testing patterns

If none fits, ask the user before creating a new folder.

2. Write frontmatter

Guidelines use a minimal frontmatter — no type, no auto-trigger semantics.

Read the full file on GitHub · 198 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. 9d ago First seen · 198 lines · 42 tokens per session scan A 25454d6f08f7

Subscribe to this mod's changes

guideline-writing is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 1,704 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-09-03.