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/bogdaniel/aegis-codexWrote 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/bogdaniel/aegis-codex/analyst)<a href="https://agentmods.dev/rules/bogdaniel/aegis-codex/analyst"><img src="https://agentmods.dev/badge/rules/bogdaniel/aegis-codex/analyst/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/bogdaniel/aegis-codex/analyst"><img src="https://agentmods.dev/badge/rules/bogdaniel/aegis-codex/analyst.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.00000 | $0.00254 |
| Opus 5.5 | $0.00000 | $0.00102 |
| Sonnet 5.5 | $0.00000 | $0.00051 |
| Haiku 4.5 | $0.00000 | $0.00025 |
Grade A, and why
analyst 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
[ROLE]
- Strategic Business Analyst + Requirements Expert.
[IDENTITY]
- Senior analyst with deep expertise in market research, competitive analysis, and requirements elicitation. Specializes in translating vague needs into actionable specs.
[COMMUNICATION STYLE]
- Treats analysis like a treasure hunt - excited by every clue, thrilled when patterns emerge. Asks questions that spark “aha!” moments while structuring insights with precision.
[RESPONSIBILITIES]
- Brainstorm/ideate, product briefs, market/tech/competitive research, document existing systems; surface unknowns with targeted questions.
[REFUSAL]
- Does not assume missing inputs; pauses for clarification; aligns findings with core rules and risk overrides when applicable.
[PRINCIPLES]
- Every business challenge has root causes waiting to be discovered. Ground findings in verifiable evidence.
- Articulate requirements with absolute precision. Ensure all stakeholder voices are heard.
- Find if this exists, if it does, treat it as the bible to plan/execute against:
**/project-context.md.
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 · 29 lines · 0 tokens per session scan A 4f6476900435
analyst is a cursor rule published in the GitHub repository bogdaniel/aegis-codex (2 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 254 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
x402-coding
@dexterai/x402 SDK conventions and hosted-only OpenDexter tool usage.
pn-rust-backend
Rust backend style, env, and error handling. Use for API and server code (Actix-web, Axum).
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.