AiSOC is an open-source, self-hostable security operations center in which an AI agent investigates alerts and supports security triage. Security teams use it for alert analysis, incident investigation, detection engineering, and purple-team exercises, while its instruction in the catalogue guides agent behavior.
Borrowing it
Nothing to install: this file belongs to beenuar/AiSOC. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/beenuar/AiSOC/main/AGENTS.mdgit clone --depth 1 https://github.com/beenuar/AiSOCWrote 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/instructions/beenuar/aisoc/agents-md)<a href="https://agentmods.dev/instructions/beenuar/aisoc/agents-md"><img src="https://agentmods.dev/badge/instructions/beenuar/aisoc/agents-md/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/instructions/beenuar/aisoc/agents-md"><img src="https://agentmods.dev/badge/instructions/beenuar/aisoc/agents-md.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.02084 | $0.02084 |
| Opus 5.5 | $0.00834 | $0.00834 |
| Sonnet 5.5 | $0.00417 | $0.00417 |
| Haiku 4.5 | $0.00208 | $0.00208 |
Grade A, and why
AiSOC 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 4d 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working in this repository
AiSOC is an open-source, AI-assisted Security Operations Center: telemetry comes in from your own security tools, gets normalized, matched against a detection corpus, correlated into alerts, triaged by an agent, and acted on through governed response verbs. It runs on your own infrastructure — cloud or on-premises — under the MIT license.
This file is for anyone changing the code, human or AI. It is the short version; each section points at the thing that is authoritative. If this file and the tree disagree, the tree is right and this file is a bug.
Get it running
make up # CORE profile: 16 long-running services, ~8 GB memory, ~20 GB disk
make doctor # what is up, what is not, and what to do about it
make smoke # the golden pipeline, eight stages, end to end
make up generates real secrets into .env, creates an administrator and
prints its password once. There is no step where you hand-edit a compose file.
make up-full adds the rest (21 services, ~12 GB) and switches on the lake
writer and the entity graph.
A first run shows real data with no credentials configured: the CISA Known Exploited Vulnerabilities catalogue is a genuine public feed that needs no API key, and a small local model does the triage.
The shape of the system
One event's journey, which is the thing worth understanding first:
connector → services/ingest → Kafka raw_events → services/fusion → Postgres alerts
polls a normalizes to the spine archives to the + services/realtime
vendor OCSF, projects lake, matches pushes to the console
API actor/action/ detections, ↓
resource/location correlates, services/agents
promotes triages with an LLM
↓
services/actions
executes a governed verb
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.
- 4d ago Changed 1b6b70cbba65
- 17d ago Changed · +99 lines · -4,662 tokens per session 5179ced95251
- 1mo ago Changed · +249 tokens per session c35da2e121dc
- 1mo ago First seen · 87 lines · 6,497 tokens per session scan A afa70f612b10
AiSOC AGENTS.md is an instructions file published in the GitHub repository beenuar/AiSOC (3,983 stars, last pushed today), licensed MIT. It adds 2,084 tokens to every session, about $0.0083 per session on Opus 5.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-30.
Other instructions, from other repositories
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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.