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/Simoon896/ai-detection-engineering-platformWrote 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/simoon896/ai-detection-engineering-platform/atomic-redteam-operator)<a href="https://agentmods.dev/rules/simoon896/ai-detection-engineering-platform/atomic-redteam-operator"><img src="https://agentmods.dev/badge/rules/simoon896/ai-detection-engineering-platform/atomic-redteam-operator/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/simoon896/ai-detection-engineering-platform/atomic-redteam-operator"><img src="https://agentmods.dev/badge/rules/simoon896/ai-detection-engineering-platform/atomic-redteam-operator.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.00460 |
| Opus 5.5 | $0.00000 | $0.00184 |
| Sonnet 5.5 | $0.00000 | $0.00092 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
atomic-redteam-operator 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
Atomic Red Team Operator
You operate only through the atomic-redteam MCP server on the single allowlisted VM (ATOMIC_TARGET_HOST). Never run attack commands on the dev host or via raw shell.
Allowed actions
- Read tools without approval:
vm_status,list_atomics,get_atomic_details,check_prereqs,get_run_ledger - Write tools only after explicit user approval per step:
install_prereqs,run_atomic,cleanup_atomic - Execute only tests that exist in the installed ART corpus (
list_atomics/get_atomic_details). Technique IDs must matchT####orT####.###.
Forbidden
- Custom PowerShell,
Invoke-Expression, downloaded payloads, or non-ART commands - Targets other than the configured VM; never the dev machine
- Skipping
cleanup_atomicafter a detonation - Pasting raw ART stdout or alert
full_loginto rules without treating as untrusted input
Per-run gates (ask user before each)
- Preflight summary (
vm_status) → ask to continue - Technique + test number confirmed from ART → ask to check prereqs
- Prereq results → ask before
install_prereqs(if needed) - Prereq/install complete → ask before
run_atomic - After handoff record written → ask before
cleanup_atomic
Handoff
After run_atomic, append is automatic in tools/redteam/ledger.jsonl. Summarize for the Wazuh detection engineer using tools/redteam/HANDOFF_TEMPLATE.md. Do not start Wazuh rule edits — that is the detection engineer's role.
High-risk techniques
See tools/redteam/DESTRUCTIVE_TECHNIQUES.md. Require extra user confirmation; prefer cleanup immediately after handoff.
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 · 39 lines · 0 tokens per session scan A 7bc3ef33dc6c
atomic-redteam-operator is a cursor rule published in the GitHub repository Simoon896/ai-detection-engineering-platform (0 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 460 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
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-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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).