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.
git clone --depth 1 https://github.com/markmhendrickson/foundationWrote 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/markmhendrickson/foundation/file_naming)<a href="https://agentmods.dev/rules/markmhendrickson/foundation/file_naming"><img src="https://agentmods.dev/badge/rules/markmhendrickson/foundation/file_naming/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.
<a href="https://agentmods.dev/rules/markmhendrickson/foundation/file_naming"><img src="https://agentmods.dev/badge/rules/markmhendrickson/foundation/file_naming.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00027 | $0.00330 |
| Opus 5.5 | $0.00011 | $0.00132 |
| Sonnet 5.5 | $0.00005 | $0.00066 |
| Haiku 4.5 | $0.00003 | $0.00033 |
Grade A, and why
file_naming 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 1mo 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.
What it actually says
File and Folder Naming Convention
All filenames and folder names must use underscores (snake_case), not kebab-case (dashes).
Format
Files:
- Correct:
create_feature_unit.md,setup_cursor_copies.md,run_feature_workflow.md - Incorrect:
create-feature-unit.md,setup-cursor-copies.md,run-feature-workflow.md
Folders:
- Correct:
cursor_rules/,feature_units/,agent_instructions/,repo_adapters/ - Incorrect:
cursor-rules/,feature-units/,agent-instructions/,repo-adapters/(use underscores:cursor_rules/,feature_units/,agent_instructions/,repo_adapters/)
When Creating or Renaming
- Use underscores (snake_case) for all filenames and folder names
- Use underscores when referencing files or folders in documentation
- Symlinks automatically use
foundation_prefix (e.g.,foundation_create_feature_unit.md)
Migration
If existing files or folders use kebab-case:
- Rename from
command-name.mdtocommand_name.mdorfolder-name/tofolder_name/ - Update references in
foundation_config.yaml, documentation files, and scripts - Run
setup_cursor_rules.shto update symlinks
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.
- 1mo ago First seen · 32 lines · 27 tokens per session scan A db251f285187
file_naming is a cursor rule published in the GitHub repository markmhendrickson/foundation (2 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 330 once invoked, about $0.0001 per session on Opus 5.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-31.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.