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/night4me/pfsense-mcp-server/agents-mdgit clone --depth 1 https://github.com/night4me/pfsense-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/night4me/pfsense-mcp-server/agents-md)<a href="https://agentmods.dev/instructions/night4me/pfsense-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/night4me/pfsense-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.1 | $0.02371 | $0.02371 |
| Opus 5 | $0.01185 | $0.01185 |
| Sonnet 5 | $0.00474 | $0.00474 |
| Haiku 4.5 | $0.00237 | $0.00237 |
Grade A, and why
pfsense-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 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pfSense MCP Server
This repository implements a security-focused MCP server for pfSense. Its current production capability profile is READ-only. Tier 0 WRITE infrastructure exists but remains inert: no WRITE tools register, the WRITE endpoint allow-list is empty, and WRITE capabilities are inactive.
Architecture and security
- Preserve the existing capability-gated architecture and current GET-only production behavior.
- Do not activate WRITE capabilities or add MCP tools unless explicitly requested and approved.
- Never weaken the security model. Secrets must not appear in MCP schemas, model outputs, logs, exceptions, fixtures, or documentation.
- Treat backward compatibility as important unless a security fix requires a breaking change.
- Refer to
README.mdfor architecture and usage anddocs/SECURITY_MODEL.mdfor the detailed trust and data model.
Development workflow
Before starting any new work session, read these files in order:
AGENTS.mdreports-ai/AI_CONTEXT.mdreports-ai/latest.mdreports-ai/NEXT_TASKS.md
Treat them as the authoritative project context. Do not base decisions only on
Git history. reports-ai is a local, Git-ignored symbolic link to an
external, maintainer-controlled directory outside this repository. Its own
reports-ai/README.md is the full entry point for that directory's structure,
authority, and update responsibilities — read it once per session alongside
the four files above; this section states only the minimum required order.
Read reports-ai/CHANGELOG_AI.md or files under reports-ai/handoff/ only
when additional historical context is required. Durable architecture
decisions and specifications live under versioned docs/adr/ and
docs/tier1/specs/ in this Git repository, never under reports-ai/ — see
reports-ai/README.md for why that split is deliberate.
For substantial tasks:
- Inspect the codebase first.
- Produce and maintain a short implementation plan.
- Make incremental, minimal changes.
- Run appropriate verification before reporting completion.
- Never claim verification that was not executed.
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 · 225 lines · 2,371 tokens per session scan A a1badc896d27
pfsense-mcp-server AGENTS.md is an instructions file published in the GitHub repository night4me/pfsense-mcp-server (7 stars, last pushed yesterday), licensed MIT. It adds 2,371 tokens to every session, about $0.0119 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
reddit-mcp CLAUDE.md
Claude Code instructions for DarkoKuzmanovic-archived/reddit-mcp, covering reddit-mcp, tech stack, commands, project structure and key design decisions.
openrouter-mcp-multimodal AGENTS.md
AGENTS.md instructions for stabgan/openrouter-mcp-multimodal, covering agent instructions, before you ship, releasing (read this before publishing), short version and version files (must all match package.json).
swag-mcp CLAUDE.md
Claude Code instructions for jmagar/swag-mcp, covering swag mcp - claude memory reference, project overview, core architecture, key components and common development commands.
sui-mcp CLAUDE.md
Claude Code instructions for 0xfreak0/sui-mcp, covering sui-mcp, stack, architecture, which transport to use and archive fallback.
clawstash CLAUDE.md
Claude Code instructions for fo0/clawstash, covering claude.md -- project guide, session start -- read order, workflow triggers, output languages and performance / modes.
swiss-procurement-mcp CLAUDE.md
Claude Code instructions for malkreide/swiss-procurement-mcp, covering claude.md, teil 1 — portfolio-konventionen, vor der arbeit, tests and wenn etwas rot ist.