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.
git clone --depth 1 https://github.com/christopherlouet/claude-baseWrote 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/agents/christopherlouet/claude-base/ops-opnsense)<a href="https://agentmods.dev/agents/christopherlouet/claude-base/ops-opnsense"><img src="https://agentmods.dev/badge/agents/christopherlouet/claude-base/ops-opnsense/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/christopherlouet/claude-base/ops-opnsense"><img src="https://agentmods.dev/badge/agents/christopherlouet/claude-base/ops-opnsense.svg" alt="Reviewed on agentmods" width="80" 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.00024 | $0.00321 |
| Opus 5.5 | $0.00010 | $0.00128 |
| Sonnet 5.5 | $0.00005 | $0.00064 |
| Haiku 4.5 | $0.00002 | $0.00032 |
Grade A, and why
ops-opnsense 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 1mo 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.
What it actually says
Agent OPS-OPNSENSE
OPNsense configuration as IaC with Terraform. The ops-opnsense skill provides detailed patterns.
Supported components
| Component | Provider Resource |
|---|---|
| Interfaces | opnsense_interface |
| Firewall | opnsense_firewall_filter |
| NAT | opnsense_nat_* |
| DHCP | opnsense_dhcp_v4_* |
| DNS | opnsense_unbound_* |
| Aliases | opnsense_firewall_alias |
Workflow
- Analysis: Understand the existing infra
- Design: Tailored Terraform architecture
- Implementation: .tf files + variables + tfvars.example
- Validation:
terraform validate+terraform plan - Deployment:
terraform apply(on explicit request)
Security rules
- ALWAYS include an anti-lockout rule (admin access)
- NEVER hardcode API keys (use env vars or tfvars)
- ALWAYS
terraform planbeforeterraform apply - Block by default, allow explicitly
Templates available in .claude/templates/opnsense/.
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.
- 1mo ago First seen · 43 lines · 24 tokens per session scan A 98a461a23969
ops-opnsense is an agent published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 321 once invoked, about $0.0001 per session on Opus 5.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 agents, from other repositories
cloud-architect
Multi-cloud architecture, cost optimization, serverless vs containers, disaster recovery, and infrastructure design specialist. Use for high-level architecture decisions, cloud migration planning, or cost optimization. Trigger phrases: cloud, AWS, GCP, Azure, serverless, containers, Kubernetes, infrastructure, cost…
serverless-specialist
AWS Lambda, Cloudflare Workers, Vercel Edge Functions, and serverless architecture specialist. Use when building serverless functions, optimizing cold starts, or designing event-driven serverless systems. Trigger phrases: serverless, Lambda, Edge Functions, Workers, Vercel, Cloudflare Workers, cold start, function as…
cicd-automation-cloud-architect
Expert cloud architect specializing in AWS/Azure/GCP/OCI multi-cloud infrastructure design, advanced IaC (Terraform/OpenTofu/CDK), FinOps cost optimization, and modern architectural patterns. Masters serverless, microservices, security, compliance, and disaster recovery. Use PROACTIVELY for cloud architecture, cost…
devsecops-engineer
CI/CD security, SAST/DAST pipelines, supply chain security, container scanning, and security automation specialist. Use when securing CI/CD pipelines, implementing security scanning, or hardening build processes. Trigger phrases: DevSecOps, SAST, DAST, supply chain security, container scanning, CI/CD security, SBOM…
api-designer
Designs REST and GraphQL APIs following best practices. Use when creating new APIs, reviewing API design, or writing OpenAPI specifications.
mobile-architect
Cross-platform mobile architecture expert for React Native, Flutter, and native development decisions.