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/amittell/firewalla-mcp-server/claude-mdgit clone --depth 1 https://github.com/amittell/firewalla-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/amittell/firewalla-mcp-server/claude-md)<a href="https://agentmods.dev/instructions/amittell/firewalla-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/amittell/firewalla-mcp-server/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.03288 | $0.03288 |
| Opus 5 | $0.01644 | $0.01644 |
| Sonnet 5 | $0.00658 | $0.00658 |
| Haiku 4.5 | $0.00329 | $0.00329 |
Grade A, and why
firewalla-mcp-server 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 5d 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 — 397 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.
CRITICAL: Before Any API Development
READ FIRST: /docs/firewalla-api-reference.md - Complete Firewalla API specification
Key Rules:
- ONLY use endpoints documented in
/docs/firewalla-api-reference.md - NEVER assume endpoints exist without verification
- ALWAYS use box-specific routing:
/v2/boxes/{box_gid}/{resource} - NEVER use fictional endpoints like
/stats/simpleor/trends/flows - ALWAYS implement client-side aggregation for bandwidth/trends
Project Overview
A Model Context Protocol (MCP) server that provides Claude with access to Firewalla firewall data. Features a 28-tool architecture with advanced search capabilities.
Architecture Overview
28-Tool Architecture
- 23 Direct API Tools: Mapping to Firewalla MSP API endpoints
- 5 Convenience Wrapper Tools: Client-side enhanced functionality for common operations
- CRUD Operations: Create, Read, Update, Delete operations for all resources
Tool Categories (28 total)
- Security (2 tools): get_active_alarms, get_specific_alarm
- Network (1 tool): get_flow_data
- Device (1 tool): get_device_status
- Rules (8 tools): get_network_rules, pause_rule, resume_rule, get_target_lists, get_specific_target_list, create_target_list, update_target_list, delete_target_list
- Search (3 tools): search_flows, search_alarms, search_rules
- Analytics (8 tools): get_boxes, get_simple_statistics, get_statistics_by_region, get_statistics_by_box, get_flow_insights, get_flow_trends, get_alarm_trends, get_rule_trends
- Convenience Wrappers (5 tools): get_bandwidth_usage, get_offline_devices, search_devices, search_target_lists, get_network_rules_summary
Development Commands
Setup and Installation
npm install
npm run build
Development
npm run dev # Build and start development server
npm run build # Build TypeScript to JavaScript
npm run build:clean # Clean build directory and rebuild
npm run start # Start built server
npm run mcp:start # Build and start MCP server
npm run mcp:test # Test MCP server connection
npm run mcp:debug # Debug MCP server with logging
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.
- 5d ago First seen · 397 lines · 3,288 tokens per session scan A db4461530b78
firewalla-mcp-server CLAUDE.md is an instructions file published in the GitHub repository amittell/firewalla-mcp-server (33 stars, last pushed 9d ago), licensed MIT. It adds 3,288 tokens to every session, about $0.0164 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.