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/flagify-com/soar-mcp/claude-mdgit clone --depth 1 https://github.com/flagify-com/soar-mcpWrote 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/flagify-com/soar-mcp/claude-md)<a href="https://agentmods.dev/instructions/flagify-com/soar-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/flagify-com/soar-mcp/claude-md.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 | $0.01618 | $0.01618 |
| Opus 5 | $0.00809 | $0.00809 |
| Sonnet 5 | $0.00324 | $0.00324 |
| Haiku 4.5 | $0.00162 | $0.00162 |
Grade A, and why
soar-mcp CLAUDE.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 3d 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
This is a SOAR MCP Server (v1.5.2) designed specifically for the OctoMation SOAR Platform. It bridges SOAR (Security Orchestration, Automation and Response) capabilities to AI clients through the Model Context Protocol (MCP).
Architecture
Core Components
soar_mcp_server.py- Main FastMCP server implementing MCP tools, resources, Flask admin app, periodic sync, and entry pointmodels.py- SQLAlchemy database models (BigInteger IDs) and Pydantic schemas;DatabaseManageruses@contextmanagersessionssync_service.py- Asynchronous service for syncing data from OctoMation SOAR API viahttpx.AsyncClientauth_utils.py- Authentication management: bcrypt password hashing, JWT with persistent secret keyconfig_manager.py- Thread-safe configuration management with database persistence and cacheauth_provider.py- SOAR authentication provider for MCP integration; dual-mode auth: HTTP Bearer Token (recommended) + URL query parameter (compatible)logger_config.py- Centralized logging withRotatingFileHandler(10MB/file, 5 backups)
Dual Server Architecture
The system runs two servers simultaneously:
- MCP Server (default port 12345): FastMCP-based server providing MCP tools and resources
- Web Admin Server (default port 12346): Flask-based web management interface
Both default to binding on 127.0.0.1 (configurable via BIND_HOST).
MCP Tools (Available to AI Clients)
list_playbooks_quick- Get concise playbook list (ID, name, displayName) — syncquery_playbook_execution_params- Get playbook parameter definitions — syncexecute_playbook- Execute SOAR playbooks with parameters — async (httpx)query_playbook_execution_status_by_activity_id- Check execution status — asyncquery_playbook_execution_result_by_activity_id- Get detailed results — async
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.
- 3d ago First seen · 184 lines · 1,618 tokens per session scan A de0d8e36f213
soar-mcp CLAUDE.md is an instructions file published in the GitHub repository flagify-com/soar-mcp (17 stars, last pushed 4mo ago), licensed MIT. It adds 1,618 tokens to every session, about $0.0081 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-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).
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.
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.
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 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).
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.