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/shigechika/cloudarmor-mcp/claude-mdgit clone --depth 1 https://github.com/shigechika/cloudarmor-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/shigechika/cloudarmor-mcp/claude-md)<a href="https://agentmods.dev/instructions/shigechika/cloudarmor-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/shigechika/cloudarmor-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.01983 | $0.01983 |
| Opus 5 | $0.00992 | $0.00992 |
| Sonnet 5 | $0.00397 | $0.00397 |
| Haiku 4.5 | $0.00198 | $0.00198 |
Grade A, and why
cloudarmor-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 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Guidance for AI assistants (and humans) editing this repository.
This file covers how to work here: commands, layout, conventions, and
the traps. Two sibling files carry the other halves and are not repeated
here — .github/copilot-instructions.md explains why the invariants
exist, and REVIEW.md decides what a reviewer treats as blocking.
What this repository is
An MCP server that reads Google Cloud Armor WAF deny logs out of Cloud
Logging and reports them: per-rule counts, a home-region false-positive
lens, and preview (dry-run) rule review. Built on the official MCP
Python SDK (mcp.server.fastmcp), published to PyPI as
cloudarmor-mcp.
Read-only by design. Every tool only reads Cloud Logging, and the
service account is documented as holding roles/logging.viewer and
nothing else. That is a security posture the deployment guide promises
to operators, not just a feature boundary.
Commands
uv sync --dev # install, including pytest + ruff
uv run pytest # unit tests (no network, no GCP creds)
uv run ruff check . # lint — gated in CI
uv run ruff format --check . # format — gated in CI (see the trap below)
uv run cloudarmor-mcp --check # live health probe against a real project
uv run cloudarmor-mcp --brief # render the daily brief to stdout
uv run python scripts/smoke_test.py # every tool against a real project
tests/ runs without network access or Google credentials:
test_client.py covers filter construction and config parsing,
test_server.py injects a fake log client. The live check is
scripts/smoke_test.py, run on a schedule against a deployed instance —
it is deliberately not part of the unit suite.
CLI exit codes (cloudarmor_mcp/__main__.py)
CLOUDARMOR_PROJECT is checked first, before either flag is handled, and
exits 1 on its own. So:
| Invocation | 0 | 1 | 2 |
|---|---|---|---|
--version |
always | — | — |
--check |
healthy | CLOUDARMOR_PROJECT unset |
degraded (probe failed) |
--brief |
every section rendered | CLOUDARMOR_PROJECT unset, or any section's query failed |
— |
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 First seen · 147 lines · 1,983 tokens per session scan A fef8b7dcb6fa
cloudarmor-mcp CLAUDE.md is an instructions file published in the GitHub repository shigechika/cloudarmor-mcp (0 stars, last pushed 8d ago), licensed MIT. It adds 1,983 tokens to every session, about $0.0099 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.
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).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.