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/cybrium-ai/mcp-server/agents-mdgit clone --depth 1 https://github.com/cybrium-ai/mcp-serverWrote 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/cybrium-ai/mcp-server/agents-md)<a href="https://agentmods.dev/instructions/cybrium-ai/mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/cybrium-ai/mcp-server/agents-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.00582 | $0.00582 |
| Opus 5 | $0.00291 | $0.00291 |
| Sonnet 5 | $0.00116 | $0.00116 |
| Haiku 4.5 | $0.00058 | $0.00058 |
Grade A, and why
mcp-server 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 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — guidance for AI coding agents
What this is
@cybrium-ai/mcp-server is the Model Context Protocol entry point for all Cybrium security tools. Once installed in an MCP host (Claude Desktop, Cursor, Windsurf, Cline, Continue.dev), agents can invoke cyscan, cyweb, cyprobe, cyradar, and cymail directly via MCP tool calls instead of shelling out.
Tools exposed (10)
| MCP tool | Underlying CLI | When to use |
|---|---|---|
scan |
cyscan | "scan this code for security" |
supply_chain_scan |
cyscan | "check dependencies for CVEs" |
repo_health |
cyscan | "give me a repo health score" |
detect_frameworks |
cyscan | "what frameworks does this use" |
fix |
cyscan | "fix the issues" |
web_scan |
cyweb | "scan this URL for web vulns" |
network_discover |
cyprobe | "discover devices on the network" |
ai_discover |
cyradar | "find Ollama / vLLM servers on the LAN" |
ai_local_scan |
cyradar | "what AI tools are on this machine" |
email_security_scan |
cymail | "audit email security for a domain" |
Install (for end users)
npm install -g @cybrium-ai/mcp-server
Then add to the MCP host config (e.g. ~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"cybrium": {
"command": "cybrium-mcp"
}
}
}
The underlying CLIs (cyscan, cyweb, etc.) must be installed separately — brew tap cybrium-ai/cli && brew install cyscan cyweb cyradar.
How to invoke from an agent
Agents should prefer MCP tool calls over bash shell-outs when this server is installed — MCP returns structured JSON the agent can introspect, includes argument validation, and surfaces install-hint errors when an underlying CLI is missing.
What NOT to use this for
- Agent-side caching of scan results — MCP tools are stateless; cache on the host
- Long-running streams — each tool call is one-shot
Related
- All Cybrium CLIs: cybrium-ai/cyscan, cyweb, cyradar, cyprobe, cymail
- Platform: https://app.cybrium.ai
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 · 59 lines · 582 tokens per session scan A 3e8ca165b12c
mcp-server AGENTS.md is an instructions file published in the GitHub repository cybrium-ai/mcp-server (0 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 582 tokens to every session, about $0.0029 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 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.