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 skills/simoon896/ai-detection-engineering-platform/atomic-redteam-safe-executionnpx skills add Simoon896/ai-detection-engineering-platform --skill atomic-redteam-safe-executiongit 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/skills/simoon896/ai-detection-engineering-platform/atomic-redteam-safe-execution)<a href="https://agentmods.dev/skills/simoon896/ai-detection-engineering-platform/atomic-redteam-safe-execution"><img src="https://agentmods.dev/badge/skills/simoon896/ai-detection-engineering-platform/atomic-redteam-safe-execution.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.00070 | $0.00950 |
| Opus 5 | $0.00035 | $0.00475 |
| Sonnet 5 | $0.00014 | $0.00190 |
| Haiku 4.5 | $0.00007 | $0.00095 |
Grade A, and why
atomic-redteam-safe-execution 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atomic Red Team Safe Execution
Scope
- MCP server:
atomic-redteam(http://127.0.0.1:3001/mcp) - Target: single VM in
.env.atomic.local(ATOMIC_TARGET_HOST) - Wazuh agent name:
ATOMIC_WAZUH_AGENT_NAME(currentlywindowsTest) - Full playbook: docs/atomic-redteam-safety.md
Iron rules
- ART only — Use
Invoke-AtomicTestindirectly via MCPrun_atomic. Never craft attack commands. - MCP only — No direct WinRM, SSH, or local PowerShell on the VM from the agent.
- One test at a time — Single
technique+test_numberper approved detonation. - Approve every phase — Stop and ask the user before each gated step (see workflow).
- Always cleanup —
cleanup_atomicafter handoff, even if the test failed or alerts were empty. - Never allowlisted — Do not assume
run_atomic/cleanup_atomicauto-run; user must approve in Cursor.
Workflow
Copy and track:
- [ ] Phase 0: Preflight (read-only)
- [ ] Phase 1: Select test (ART catalog only)
- [ ] Phase 2: Prereqs
- [ ] Phase 3: Install prereqs (if needed)
- [ ] Phase 4: Detonate (run_atomic)
- [ ] Phase 5: Handoff
- [ ] Phase 6: Cleanup
- [ ] Phase 7: User summary
Phase 0 — Preflight (read-only)
Tools: vm_status, optionally get_run_ledger
Report: transport, target, hostname, PS version, agent name.
Ask: "Preflight OK. Proceed to technique selection?"
Phase 1 — Select test (ART catalog only)
Tools: list_atomics, get_atomic_details
- User must pick or confirm technique + test number from ART YAML.
- Reject unknown IDs or tests not in
get_atomic_details. - Check tools/redteam/DESTRUCTIVE_TECHNIQUES.md; flag high-risk tests.
Ask: "Run prereq check for Txxxx test N?"
Phase 2 — Prereqs (read-only)
Tool: check_prereqs
Summarize missing prereqs without installing yet.
Ask: "Install prereqs?" only if something is missing.
Phase 3 — Install prereqs (gated)
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.
- 5d ago First seen · 105 lines · 70 tokens per session scan A c004795563c9
atomic-redteam-safe-execution is a skill published in the GitHub repository Simoon896/ai-detection-engineering-platform (0 stars, last pushed 2mo ago), licensed MIT. It adds 70 tokens to every session and 950 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…