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/configuration_management)<a href="https://agentmods.dev/rules/markmhendrickson/foundation/configuration_management"><img src="https://agentmods.dev/badge/rules/markmhendrickson/foundation/configuration_management/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/configuration_management"><img src="https://agentmods.dev/badge/rules/markmhendrickson/foundation/configuration_management.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.00025 | $0.00994 |
| Opus 5.5 | $0.00010 | $0.00398 |
| Sonnet 5.5 | $0.00005 | $0.00199 |
| Haiku 4.5 | $0.00003 | $0.00099 |
Grade A, and why
configuration_management 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.
How it starts
The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configuration Management Rule
Ensures configuration files are placed in the correct location based on their scope and purpose.
Configuration Locations
Repository-Specific Configuration
Location: foundation-config.yaml in the repository root (NOT in foundation submodule)
Contains:
- Repository name, type, and languages
- Development workflow settings (branch strategy, commit format, PR settings)
- Code conventions specific to this repository
- Testing configuration
- Documentation standards
- Security settings (protected paths, credential management)
- Tooling configuration
- Agent instructions configuration
- Repository-specific custom settings
Example:
# foundation-config.yaml (in repository root)
repository:
name: "my-project"
type: "application"
conventions:
python:
files: "snake_case"
security:
pre_commit_audit:
protected_paths:
- "data/imports/" # Repository-specific paths
Shared Configuration (Repo Adapters)
Location: foundation/config/repo-adapters/<repo-name>.yaml (in foundation submodule)
Purpose: Shared configurations used across MULTIPLE repositories with the same name/type
When to use:
- Configuration shared across multiple repositories (e.g., all "neotoma" repos)
- Template configurations for similar project types
- Organization-wide standards
When NOT to use:
- Single repository configuration
- Repository-specific paths or settings
- Unique repository requirements
Example:
# foundation/config/repo-adapters/neotoma.yaml
# Used by ALL neotoma-related repositories
repo_name: "neotoma"
conventions:
typescript:
files: "snake_case"
documentation:
required_sections:
- "Agent Instructions" # Standard for all neotoma repos
Rules
MUST
- Repository-specific config → repository's
foundation-config.yaml- All configuration unique to a single repository goes in the repository's own
foundation-config.yaml - Includes: conventions, security paths, documentation structure, custom settings
- All configuration unique to a single repository goes in the repository's own
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 · 157 lines · 25 tokens per session scan A 8e6d17f20891
configuration_management is a cursor rule published in the GitHub repository markmhendrickson/foundation (2 stars, last pushed 2mo ago), licensed MIT. It adds 25 tokens to every session and 994 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.