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-inventory)<a href="https://agentmods.dev/rules/contoso-state/red-team-agent-orchestration/redteam-inventory"><img src="https://agentmods.dev/badge/rules/contoso-state/red-team-agent-orchestration/redteam-inventory/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/contoso-state/red-team-agent-orchestration/redteam-inventory"><img src="https://agentmods.dev/badge/rules/contoso-state/red-team-agent-orchestration/redteam-inventory.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.00044 | $0.00385 |
| Opus 5 | $0.00022 | $0.00192 |
| Sonnet 5 | $0.00009 | $0.00077 |
| Haiku 4.5 | $0.00004 | $0.00038 |
Grade A, and why
redteam-inventory 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 10d 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 — Inventory & Scope (Preflight)
You confirm authorization and produce the resource inventory the whole team depends on.
Methodology: agents/inventory-scope/system-prompt.md. Commands: tools/az-cli/README.md (preflight).
Skill (domain knowledge): .github/skills/azure-redteam-inventory/SKILL.md.
Steps
az account show/az account list— confirm identity and accessible subscriptions.- Validate effective RBAC for
Reader,Security Reader,Log Analytics Reader,Directory Reader,Key Vault Reader. Record any gap as a coverage limitation (don't fail). - Enumerate resources via Resource Graph:
az graph query -q "Resources | project id,type,name,location,resourceGroup" -o json. Apply scope +exclusionsfromengagement.yaml. - Write
engagements/<session>/inventory/resources.jsonl(perschemas/inventory.schema.json),engagements/<session>/inventory/subscriptions.json, andengagements/<session>/inventory/coverage-limitations.json.
Safety
Read-only only (list/show/query). Honor exclusions strictly. Report back to the orchestrator
when the inventory is ready, with a resource-type breakdown.
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.
- 10d ago First seen · 28 lines · 44 tokens per session scan A 54dde58f59c7
redteam-inventory is a cursor rule published in the GitHub repository Contoso-State/red-team-agent-orchestration (6 stars, last pushed 5d ago), licensed MIT. It adds 44 tokens to every session and 385 once invoked, about $0.0002 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
aws-ecs
Definitive guidelines for building, deploying, and operating applications on AWS ECS, emphasizing immutable containers, secure secrets management, and robust operational patterns.
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
aws-rds-best-practices
AWS RDS PostgreSQL best practices - database configuration, connection management, authentication, backup, and performance optimization standards.
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.