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 skills add christopherlouet/claude-base --skill ops-opnsensegit 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/skills/christopherlouet/claude-base/ops-opnsense)<a href="https://agentmods.dev/skills/christopherlouet/claude-base/ops-opnsense"><img src="https://agentmods.dev/badge/skills/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/skills/christopherlouet/claude-base/ops-opnsense"><img src="https://agentmods.dev/badge/skills/christopherlouet/claude-base/ops-opnsense.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 355 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium Data Exfiltration · line 355 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00026 | $0.02854 |
| Opus 5.5 | $0.00010 | $0.01142 |
| Sonnet 5.5 | $0.00005 | $0.00571 |
| Haiku 4.5 | $0.00003 | $0.00285 |
Grade A, and why
ops-opnsense scanned grade A with 1 finding 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 27d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -k -u "api-key:api-secret" \ How it starts
The opening of the file, as written. The whole thing — 399 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OPNsense Configuration (Terraform)
Complete guide to configure OPNsense declaratively with Terraform and the browningluke/opnsense provider.
When to use this Skill
Activate this skill to:
- Configure OPNsense network interfaces (WAN, LAN, VLANs)
- Manage firewall rules
- Configure NAT and port forwarding
- Manage DHCP and DNS services
- Create aliases to simplify rules
Do not use for:
- Initial OPNsense installation (see manual documentation)
- VM provisioning (use
/ops:ops-proxmox) - Advanced OPNsense plugins (HAProxy, Suricata)
Terraform Provider
| Attribute | Value |
|---|---|
| Provider | browningluke/opnsense |
| Version | >= 0.11 |
| Documentation | https://registry.terraform.io/providers/browningluke/opnsense/latest/docs |
| GitHub | https://github.com/browningluke/terraform-provider-opnsense |
Provider Configuration
terraform {
required_providers {
opnsense = {
source = "browningluke/opnsense"
version = "~> 0.11"
}
}
}
provider "opnsense" {
uri = var.opnsense_uri # https://192.168.10.1
api_key = var.opnsense_api_key # Sensitive
api_secret = var.opnsense_api_secret # Sensitive
allow_insecure = true # false in production
}
Configuration Patterns
1. Network Interfaces
# WAN interface (DHCP from ISP box)
resource "opnsense_interface" "wan" {
device = "vtnet0"
description = "WAN - Orange Box"
ipv4_type = "dhcp"
block_private = true
block_bogons = true
}
# LAN interface (static IP)
resource "opnsense_interface" "lan" {
device = "vtnet1"
description = "LAN - Local network"
ipv4_type = "static"
ipv4_addr = "192.168.10.1"
ipv4_mask = 24
}
2. Firewall Rules (CRITICAL: Anti-lockout)
# MANDATORY: Anti-lockout rule (ALWAYS first)
resource "opnsense_firewall_filter" "anti_lockout" {
interface = "lan"
direction = "in"
action = "pass"
protocol = "tcp"
source_net = "lannet"
destination_net = "(self)"
destination_port = "443"
description = "ANTI-LOCKOUT: Admin access"
sequence = 1
}
# Allow outbound HTTP/HTTPS
resource "opnsense_firewall_filter" "lan_to_web" {
interface = "lan"
direction = "in"
action = "pass"
protocol = "tcp"
source_net = "lannet"
destination_net = "any"
destination_port = "80,443"
description = "Allow outbound HTTP/HTTPS"
sequence = 10
}
# Block everything else (deny by default)
resource "opnsense_firewall_filter" "lan_block_all" {
interface = "lan"
direction = "in"
action = "block"
protocol = "any"
source_net = "any"
destination_net = "any"
log = true
description = "Block and log everything else"
sequence = 65535
}
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.
- 27d ago Changed · -2 lines 0dc126530a77
- 28d ago Changed · -6 lines 0227daadcae7
- 29d ago Changed · -1 lines 35a1cb71e1a6
- 1mo ago First seen · 408 lines · 26 tokens per session scan A c42d0ecd6d70
ops-opnsense is a skill published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed 7d ago), licensed MIT. It adds 26 tokens to every session and 2,854 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
microservices-architecture
Microservices architecture patterns and best practices. Use when designing distributed systems, breaking down monoliths, or implementing service communication.
accessibility-a11y
WCAG 2.2 compliance, ARIA patterns, keyboard navigation, screen readers, automated testing.
event-planner
Event planning with timelines, budgets, vendor coordination, logistics checklists, and post-event evaluation. Use when organizing conferences, workshops, galas, or corporate events.
ios-development
Comprehensive guide for building native Apple platform applications.
agent-observability-engineer
Specialist subagent: OpenTelemetry, Prometheus, Grafana, distributed tracing, SLO design, and alerting specialist. Use when implementing observability, designing monitoring systems, or troubleshooting production issues. Trigger phrases: observability, monitoring, tracing, Prometheus, Grafana, OpenTelemetry, SLO, SLI…
literature-review-planner
Structured literature review planning with systematic methodology, source evaluation, and synthesis frameworks. Use when planning academic literature reviews, research surveys, systematic reviews, or scoping reviews.