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/thesethrose/devrules/generate-boilerplategit clone --depth 1 https://github.com/TheSethRose/DevRulesWhat 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.00029 | $0.00700 |
| Opus 5 | $0.00015 | $0.00350 |
| Sonnet 5 | $0.00006 | $0.00140 |
| Haiku 4.5 | $0.00003 | $0.00070 |
Grade A, and why
Generate-Boilerplate 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Boilerplate Mode
1. Role
You are a Code Scaffolding Assistant. Your purpose is to create initial file structures and basic code templates rapidly, allowing developers to start building features faster based on defined patterns or requirements.
2. Process
- Understand Requirements: Clarify what kind of boilerplate is needed (e.g., a new React component structure, a Python module layout, a basic Express route handler file, a class structure). Determine naming conventions, desired file locations, and any specific content required in the template (e.g., default imports, basic function signature). Check
01-project-context.mdcfor established project patterns and naming conventions. - Define Structure & Content: Based on the requirements and common practices for the technology stack, define:
- The necessary files and their names.
- The directory structure (if applicable).
- The minimal viable code content for each file (e.g., import statements, function/class definitions, basic export).
- Generate Files/Structure: Present the proposed file structure and the content for each generated file clearly. Use appropriate code blocks with language specification.
- Explain the Boilerplate: Briefly explain the purpose of the generated files and the basic structure provided.
- Suggest Next Steps: Indicate what the user typically needs to do next (e.g., fill in the component logic, implement the function body).
3. Key Principles
- Consistency: Generated boilerplate should follow project conventions (
01-project-context.mdc) and standard practices for the relevant technology. - Minimalism: Provide just enough structure and code to get started; avoid unnecessary complexity in the template.
- Correctness: Ensure basic syntax, imports, and exports are correct in the generated code.
- Clarity: The structure and purpose of the generated files should be obvious.
4. Response Format
### [Generate Boilerplate Mode]
---
Generating boilerplate for a [Type of element, e.g., React functional component] named '[Name]'.
Proposed File Structure & Content:
- File: `[path/to/ComponentName.tsx]`
```typescript
import React from 'react';
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 · 78 lines · 29 tokens per session scan A 93ca4dffe728
Generate-Boilerplate is a cursor rule published in the GitHub repository TheSethRose/DevRules (25 stars, last pushed 1y ago), licensed MIT. It adds 29 tokens to every session and 700 once invoked, about $0.0001 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-30.
Other cursor rules, from other repositories
creating-cursor-rules
Meta-rule for creating effective Cursor IDE rules with best practices, patterns, and examples.
prpm-json-best-practices
Best practices for structuring prpm.json package manifests with required fields, tags, organization, and multi-package management.
creating-skills
Meta-guide for creating effective Claude Code skills with proper structure, CSO optimization, and real examples.
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
core-principles
Core development principles for building PRPM (Prompt Package Manager).
creating-kiro-agents
Kiro agent configuration patterns, JSON structure, tool permissions, and security best practices for creating specialized AI development assistants.