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 instructions/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/instructions/felipebarcelospro/igniter-js/writing-guidelines)<a href="https://agentmods.dev/instructions/felipebarcelospro/igniter-js/writing-guidelines"><img src="https://agentmods.dev/badge/instructions/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.06725 | $0.06725 |
| Opus 5 | $0.03363 | $0.03363 |
| Sonnet 5 | $0.01345 | $0.01345 |
| Haiku 4.5 | $0.00673 | $0.00673 |
Grade C, and why
igniter-js writing-guidelines.instructions.md scanned grade C with 1 finding 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 3d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- Detailed instructions --> How it starts
The opening of the file, as written. The whole thing — 1,037 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.
- 3d ago First seen · 1,037 lines · 6,725 tokens per session scan C 0681e3908da1
igniter-js writing-guidelines.instructions.md is an instructions file published in the GitHub repository felipebarcelospro/igniter-js (242 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 6,725 tokens to every session, about $0.0336 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.
Other instructions, from other repositories
darto AGENTS.md
Instructions for evandersondev/darto, covering agents.md, the #1 thing to get right: context, not (req, res, next), conventions an agent won't infer, imports and repository layout.
AI-RAG-Assistant-Chatbot AGENTS.md
Instructions for hoangsonww/AI-RAG-Assistant-Chatbot, covering lumina codex guide, repository overview, scope rules, working rules and validation commands.
wa-automate-nodejs AGENTS.md
AGENTS.md instructions for open-wa/wa-automate-nodejs, covering repository instructions, commit policy, no ai attribution, commit grouping and gitmoji reference.
keryx CLAUDE.md
Instructions for actionhero/keryx, covering claude.md, project overview, monorepo structure, development environment and environment setup.
wa-automate-nodejs copilot-instructions.md
Copilot instructions for open-wa/wa-automate-nodejs, covering switchboard configuration for github, available mcp tools, messaging (cross-ide), workflow management and terminal management.
oraclaw CLAUDE.md
Claude Code instructions for Whatsonyourmind/oraclaw, covering claude.md — oraclaw v2.0 (decision intelligence platform), project overview, tech stack, project structure and build & dev commands.