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/bogdaniel/aegis-codex/00-overviewgit clone --depth 1 https://github.com/bogdaniel/aegis-codexWhat 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.00624 |
| Opus 5 | $0.00000 | $0.00312 |
| Sonnet 5 | $0.00000 | $0.00125 |
| Haiku 4.5 | $0.00000 | $0.00062 |
Grade A, and why
00-overview 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.
What it actually says
[SOURCE OF TRUTH]
- Editable source:
rules/agents/00-overview.mdc - Generated/consumed copy:
.cursor/rules/agents/00-overview.mdc(keep references intact)
[INTENT]
- Define shared agent rules, responsibilities, and blocking compliance criteria that apply to all core agents.
[APPLICABILITY]
- Applies to all core agents (
@architect,@implementer,@code-reviewer,@test-engineer,@security-auditor,@supervisor,@orchestrator) in all contexts; non-negotiable unless a valid risk override per.cursor/rules/3G-risk-overrides.mdcis explicitly invoked.
[CROSS-REFERENCES]
- Architecture/DDD:
.cursor/rules/36-architecture.mdc,.cursor/rules/44-ddd.mdc(binding) - Testing/change-discipline:
.cursor/rules/31-testing.mdc,.cursor/rules/23-change-control.mdc(binding) - Risk overrides:
.cursor/rules/3G-risk-overrides.mdc(explicit overrides only)
[AGENTS OVERVIEW]
- All agents: enforce verification artifact; respect security/testing/observability/performance/CI/API standards; fail closed if format cannot be honored.
- MANDATORY: All agents MUST treat
.cursor/rules/36-architecture.mdc,.cursor/rules/44-ddd.mdc, and relevant50-lang-*.mdcas hard constraints (not suggestions). - MANDATORY: All agents MUST reject designs/code that violate architecture doctrine (layering, bounded contexts, domain purity, path aliases, framework-free Domain/Application).
- MANDATORY: Architecture rules are non-negotiable — agents MUST refuse to implement non-compliant designs and propose compliant alternatives.
- MANDATORY: All agents MUST also enforce the change-discipline cluster (
.cursor/rules/23-change-control.mdc,.cursor/rules/45-bugfix-protocol.mdc,.cursor/rules/46-regression-discipline.mdc,.cursor/rules/47-diff-discipline.mdc,.cursor/rules/48-doc-sync.mdc,.cursor/rules/35-api-lifecycle.mdc) as binding; violations are blocking unless a valid risk override per.cursor/rules/3G-risk-overrides.mdcis in effect. - MANDATORY: Risk overrides follow
.cursor/rules/3G-risk-overrides.mdcexclusively; do not duplicate override semantics elsewhere.
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 · 40 lines · 0 tokens per session scan A 5fb7d5b89fa6
00-overview is a cursor rule published in the GitHub repository bogdaniel/aegis-codex (2 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 624 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-31.
Other cursor rules, from other repositories
checks
How to add or modify a scanner check.
http
HTTP handler conventions.
config-and-di
ArchiPy BaseConfig, FastAPIConfig/uvicorn, and DI container wiring.
using-archipy-adapters
Using and writing adapters in ArchiPy apps — extras, ports, mocks, boundary errors.
testing-bdd-for-apps
BDD testing for ArchiPy apps — Behave, ScenarioContext, testcontainers.
using-archipy-models
ArchiPy app models — DTOs, entities, errors naming and layout.