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 instructions/beenuar/aisoc/agents-mdgit clone --depth 1 https://github.com/beenuar/AiSOCWhat 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 | $0.06497 | $0.06497 |
| Opus 5 | $0.03248 | $0.03248 |
| Sonnet 5 | $0.01299 | $0.01299 |
| Haiku 4.5 | $0.00650 | $0.00650 |
Grade A, and why
AiSOC AGENTS.md scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Devcontainer prebuilt image.** `.devcontainer/devcontainer.json` prefers `ghcr.io/beenuar/aisoc-devcontainer:latest` (with local Dockerfile fallback). `.github/workflows/devcontainer-build.yml` publishes multi-arch ( How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Learned User Preferences
- Always track progress locally (e.g. in a TODO/PROGRESS file) so work can be resumed after IDE crashes or restarts.
- Complete all planned tasks without stopping mid-way; work through the full list until done.
- Do not mention competitor names (Prophet Security, Torq) anywhere in code, comments, or docs — this is an open-source project.
- Before pushing to GitHub, ensure no secrets, API keys, tokens, or sensitive data are present in any public repo files.
- Host codebase on GitHub once fully built out; keep documentation in sync.
- Never edit plan files directly — implement the plan as specified without modifying the plan document itself.
- After every significant change, push code and update documentation on GitHub immediately — don't wait to be asked.
- Benchmark data and documentation must be transparent about what is synthetic vs. real; never present fabricated metrics as actual measured performance.
- When the task is clear, act autonomously — don't ask unnecessary clarifying questions.
- Standing repo-maintenance loop is the default when no other task is queued: review open PRs at the canonical repo, resolve CI/conflicts, merge them, close issues those PRs resolved, and keep
maingreen. - After any deploy to
tryaisoc.com, do an end-to-end customer-journey review that covers the full authenticated app (registration → login → connector setup → live ingest/triage → billing), not just landing → dashboard: click through every interactive element and fix dead buttons, broken flows, and empty/errored views before declaring done. The user repeatedly reports broken authenticated features post-deploy and demands being "1000% sure" nothing is broken before any handover. - The authenticated product must run on real, live connector-ingested data and genuine LLM triage — never mock/demo/baseline-fallback or empty data presented as working. When a user connects a connector, the platform must automatically and continuously (near-real-time) pull and analyze that data for triage without the user having to ask; stubbed features, empty dashboards, and silent mock-data fallbacks are treated as bugs.
- When asked "what else can we improve?" / "what are the missing pieces?" / "make this world-class", produce a concrete competitive gap analysis vs. leading commercial AI-SOC products and implement the gaps — don't just answer in prose.
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.
- 2d 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 (2,363 stars, last pushed 2d ago), licensed MIT. It adds 6,497 tokens to every session, about $0.0325 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
Anthropic-Cybersecurity-Skills copilot-instructions.md
Copilot instructions for mukul975/Anthropic-Cybersecurity-Skills, covering copilot instructions for anthropic-cybersecurity-skills, quick facts, repository structure, build & development and prerequisites.
Anthropic-Cybersecurity-Skills AGENTS.md
AGENTS.md instructions for mukul975/Anthropic-Cybersecurity-Skills, covering agents.md, what this repository is, reading a skill, changing a skill and writing a description.
ai-dfir-toolkit CLAUDE.md
Instructions for depalmar/ai-dfir-toolkit, covering project context, what this is, commands, rules that are not negotiable and what a restricted runner cannot verify.
attackgen AGENTS.md
AGENTS.md instructions for mrwadams/attackgen, covering agents.md, project overview, development commands, running the application and installing dependencies.
attackgen CLAUDE.md
Claude Code instructions for mrwadams/attackgen, covering claude.md, project overview, development commands, running the application and installing dependencies.
cyberskills-hub CLAUDE.md
Instructions for haporfirio/cyberskills-hub, covering cyberskills documentation hub, instrucao de routing, role context, top-50 keywords and domain lookup.