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/Contoso-State/red-team-agent-orchestrationWrote 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/contoso-state/red-team-agent-orchestration/redteam-authorization)<a href="https://agentmods.dev/rules/contoso-state/red-team-agent-orchestration/redteam-authorization"><img src="https://agentmods.dev/badge/rules/contoso-state/red-team-agent-orchestration/redteam-authorization.svg" alt="Measured on agentmods" 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.00061 | $0.00373 |
| Opus 5 | $0.00030 | $0.00187 |
| Sonnet 5 | $0.00012 | $0.00075 |
| Haiku 4.5 | $0.00006 | $0.00037 |
Grade A, and why
redteam-authorization 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 8d 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
Red Team — Authorization & Attack Path
The highest-value sub-agent. Find privilege escalation and lateral movement, then chain the team's findings into attack paths an attacker would actually walk.
Methodology: agents/authorization-attack-path/system-prompt.md. Checks: checks/rbac/checks.yaml.
Skill (domain knowledge): .github/skills/azure-redteam-authorization/SKILL.md.
Az CLI runner: tools/az-cli/rbac.md. Playbook: playbooks/privilege-path-analysis.md.
Two Passes
- RBAC checks. Run
checks/rbac/checks.yamlvia the runner. Emit findingsAZ-AUTHZ-. - Correlation. Read all
engagements/<session>/findings/raw/*.jsonland build chains scored by end state, e.g.public app (network) -> managed identity (compute) -> Key Vault secret -> DB (data). Emit chain findingsAZ-PATH-withattack_pathpopulated.
Safety
Read-only analysis of permissions/relationships. Never modify role assignments; never execute an escalation. Report the top chains back to the orchestrator.
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.
- 8d ago First seen · 27 lines · 61 tokens per session scan A b7ebbcee2b2d
redteam-authorization is a cursor rule published in the GitHub repository Contoso-State/red-team-agent-orchestration (6 stars, last pushed 3d ago), licensed MIT. It adds 61 tokens to every session and 373 once invoked, about $0.0003 per session on Opus 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.
cli-error-handling
CLI command error handling patterns.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.