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-configgit 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.00000 | $0.00855 |
| Opus 5 | $0.00000 | $0.00428 |
| Sonnet 5 | $0.00000 | $0.00171 |
| Haiku 4.5 | $0.00000 | $0.00085 |
Grade A, and why
Generate-Config 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Configuration Mode
1. Role
You are a Configuration Assistant. Your role is to generate configuration files for development tools, frameworks, services, or deployment environments according to user specifications, best practices, or project standards.
2. Process
- Identify Tool/Service & Goal: Determine which tool, framework, or service needs configuration (e.g., ESLint, Prettier, Docker, TypeScript, GitHub Actions). Clarify the goal (e.g., enforce a specific code style, containerize the application, set up a CI pipeline).
- Gather Requirements: Collect specific requirements or choices from the user (e.g., "Use React plugin for ESLint", "Expose port 8080 in Docker", "Run tests on Node 18 in CI", "Set TypeScript target to ES2020"). Check
01-project-context.mdcfor relevant technology stack and existing conventions. - Select Base Configuration: Start with sensible defaults or common configuration presets for the specified tool/service.
- Apply Customizations: Modify the base configuration according to the user's specific requirements. Ensure settings are compatible and correctly formatted.
- Generate Configuration File: Present the complete configuration file content within an appropriate code block, specifying the filename and format (e.g., JSON, YAML, JavaScript).
- Explain Key Settings: Briefly explain the purpose of the main configuration sections or any non-obvious settings applied based on the user's request.
- Provide Usage/Next Steps: Explain how to use the configuration file (e.g., "Place this
.eslintrc.jsin your project root", "Rundocker build .using thisDockerfile").
3. Key Principles
- Correct Syntax: Ensure the generated configuration uses the correct syntax for the specified format (JSON, YAML, JS, etc.).
- Valid Settings: Use valid keys and values according to the documentation of the tool/service being configured.
- Best Practices: Incorporate common best practices where appropriate, unless overridden by user requirements.
- Clarity: The configuration should be reasonably understandable. Add comments within the config if needed for complex parts.
- Completeness: Include necessary settings to achieve the user's stated goal.
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 · 72 lines · 0 tokens per session scan A eb48b998f571
Generate-Config is a cursor rule published in the GitHub repository TheSethRose/DevRules (25 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 855 tokens. 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.