ai-detection-engineering-platform AGENTS.md

Repository instructions for coordinating a red-team operator and a Wazuh detection engineer through local MCP servers. Red-team testing simulates attack techniques, while Wazuh is a security monitoring platform.

In plain words
What is it for?
Use them when running Atomic Red Team tests, correlating runs with Wazuh alerts, tuning detection rules, and checking the required safety records.
Why use it?
They define safe execution, approvals, cleanup, shared records, and the handoff from simulated attacks to detection tuning.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/simoon896/ai-detection-engineering-platform/agents-md
Clone the repo
git clone --depth 1 https://github.com/Simoon896/ai-detection-engineering-platform

Made for: Codex, OpenCode.

Per session 390 This file is loaded in full into every session.
When invoked 390 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00390 $0.00390
Opus 5 $0.00195 $0.00195
Sonnet 5 $0.00078 $0.00078
Haiku 4.5 $0.00039 $0.00039

Measured yesterday against content hash 9f4c8d89cd99, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ai-detection-engineering-platform AGENTS.md 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 yesterday.

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.

AGENTS.md · 38 lines

What it actually says

Agent Roles — Wazuh + Atomic Red Team

Start here after a break: docs/ART-WAZUH-SESSION-GUIDE.md — full session summary, reboot checklist, and run-again steps.

This repo supports two cooperating Cursor agents via localhost MCP servers.

Red Team Operator

  • Server: atomic-redteam (http://127.0.0.1:3001/mcp)
  • Skill: atomic-redteam-safe-execution
  • Rule: atomic-redteam-operator
  • Docs: docs/atomic-redteam-safety.md

Runs ART tests only through MCP, with per-phase user approval and mandatory cleanup.

Wazuh Detection Engineer

  • Server: wazuh (http://127.0.0.1:3000/mcp)
  • Skill: wazuh-art-detection-handoff
  • Rule: wazuh-art-detection-loop
  • Docs: FP_TUNING.md

Correlates ledger runs with alerts; tunes rules only with user approval.

Shared artifacts

File Purpose
tools/redteam/ledger.jsonl Append-only run records
tools/redteam/HANDOFF_TEMPLATE.md Operator → detection handoff
tools/redteam/coverage.md Technique detection status
tools/redteam/SAFETY_CHECKLIST.md Per-run checklist
tools/redteam/DESTRUCTIVE_TECHNIQUES.md High-risk technique policy

MCP allowlist

Never allowlist: run_atomic, cleanup_atomic, install_prereqs, update_rule_file, wazuh_restart.

Changes

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.

  1. yesterday First seen · 38 lines · 390 tokens per session scan A 9f4c8d89cd99

Subscribe to this mod's changes

ai-detection-engineering-platform AGENTS.md is an instructions file published in the GitHub repository Simoon896/ai-detection-engineering-platform (0 stars, last pushed 1mo ago), licensed MIT. It adds 390 tokens to every session, about $0.0019 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.

Related

Other instructions, from other repositories

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,345 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens