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 rules/felipebarcelospro/igniter-js/writing-guidelinesgit clone --depth 1 https://github.com/felipebarcelospro/igniter-jsWrote 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/rules/felipebarcelospro/igniter-js/writing-guidelines)<a href="https://agentmods.dev/rules/felipebarcelospro/igniter-js/writing-guidelines"><img src="https://agentmods.dev/badge/rules/felipebarcelospro/igniter-js/writing-guidelines.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.07873 | $0.07873 |
| Opus 5 | $0.03936 | $0.03936 |
| Sonnet 5 | $0.01575 | $0.01575 |
| Haiku 4.5 | $0.00787 | $0.00787 |
Grade A, and why
writing-guidelines 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.
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 — 1,293 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Guidelines for Humans and LLMs
This guide ensures consistent, high-quality documentation across all Igniter.js content types (blog, docs, templates, updates). It's designed for both human authors and AI agents to produce excellent developer experiences.
Core Style Principles
| Principle | Definition | Example: Good | Example: Bad |
|---|---|---|---|
| Clear Language | Use simple, direct language with short words and sentences. Avoid unnecessary jargon. | "Click save to store your changes." | "Initiate the persistence process by activating the storage mechanism." |
| Developer-Focused | Write in a professional but approachable tone that addresses the reader directly. | "You can configure this option in the settings panel." | "Users might want to adjust configuration parameters." |
| Example-Driven | Include practical code examples for all key concepts. | "Use the useState hook: const [count, setCount] useState(0)" |
"State management is an important React concept." |
| Active Voice | Make the subject perform the action rather than receive it. | "React renders the component." | "The component is rendered by React." |
| Success-First | Show working examples before explaining theory. | "First, create a component: function Button() {...}. Now let's understand how it works..." |
"The component lifecycle has several phases which you must understand before implementation..." |
| Transparent | Be honest about limitations and challenges. | "This approach works well for small datasets but may cause performance issues with larger ones." | "This is the optimal solution for data management." |
| Consistent Terms | Use the same terminology throughout to refer to the same concepts. | "Route" consistently or "endpoint" consistently, not both interchangeably. | Mixing "callback function" and "handler" for the same concept. |
Fumadocs-Specific Guidelines
Igniter.js documentation uses Fumadocs, a modern documentation framework with MDX support and powerful components.
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.
- 2d ago First seen · 1,293 lines · 7,873 tokens per session scan A 0e86fabe41ba
writing-guidelines is a cursor rule published in the GitHub repository felipebarcelospro/igniter-js (242 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 7,873 tokens to every session, about $0.0394 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-01.
Other cursor rules, from other repositories
codegraph
CodeGraph MCP usage guide — when to use which tool.
git
Never mutate git history, remotes, or GitHub repo state.
css
TSF stylesheet conventions, layout debugging, and minification.
javascript
TSF JavaScript syntax, formatting, and minification.
local
Private workspace guidance and gitignored .local search (Grep/Glob are blind).
docs
Readme wording constraints, WordPress readme format, changelog prose style, and public API naming requirements.