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 fastrevmd-lab/fwskillsshare --skill csrx-proxmox-deploygit clone --depth 1 https://github.com/fastrevmd-lab/fwskillsshareWrote 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/fastrevmd-lab/fwskillsshare/csrx-proxmox-deploy)<a href="https://agentmods.dev/skills/fastrevmd-lab/fwskillsshare/csrx-proxmox-deploy"><img src="https://agentmods.dev/badge/skills/fastrevmd-lab/fwskillsshare/csrx-proxmox-deploy/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/fastrevmd-lab/fwskillsshare/csrx-proxmox-deploy"><img src="https://agentmods.dev/badge/skills/fastrevmd-lab/fwskillsshare/csrx-proxmox-deploy.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.00177 | $0.08145 |
| Opus 5.5 | $0.00071 | $0.03258 |
| Sonnet 5.5 | $0.00035 | $0.01629 |
| Haiku 4.5 | $0.00018 | $0.00814 |
Grade A, and why
csrx-proxmox-deploy 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 23d 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 — 583 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploying a Juniper cSRX Container Firewall on Proxmox VE
STATUS: draft (v0.1.0). Every claim below comes from one end-to-end build on Proxmox VE 9.2.20 running cSRX 26.2R1.7 as a Docker container, exercised in both secure-wire and routing forwarding modes. It has not been repeated on a different cSRX release or a second Proxmox estate. No vendor release notes existed for the build this content is drawn from — the image's own init scripts were the source of truth throughout, and that method is preserved here (§ "Rediscovering the CSRX_* surface") so it transfers to a release this skill has not seen. Values in
<angle brackets>are site-specific.
Overview
The two findings that cost the most time, first in Gotchas below: (1) The reference guest's CPU model did not expose SSSE3, and cSRX's forwarding process hard-requires it even when its DPDK fast-path driver is not selected — the container comes up
Upand healthy with zero forwarding plane underneath it. Whether a given guest's default CPU model exposes SSSE3 depends on the Proxmox version and how the guest was created (qm createCLI vs the web UI), so this must be verified rather than assumed. (2) Docker's default macvlanbridgemode structurally cannot deliver a frame addressed to a foreign MAC — exactly what a bump-in-the-wire firewall needs — regardless of promiscuous-mode settings on either end. The pre-power-on gate exists specifically to catch both before a live build re-discovers them the hard way.
cSRX ships as a Docker image, not a VM appliance — there is no qcow2, no raw
disk, no ISO. Deployment is therefore: build a KVM guest (not an LXC —
cSRX runs --privileged and manipulates its own network namespace, which an
LXC's nesting makes unworkable to debug) running Docker CE, with one
management NIC and at least two data-plane NICs; wire the data-plane NICs to
Docker macvlan networks in passthru mode; and run the cSRX container
against that image with the CSRX_* environment-variable surface set for
the chosen forwarding mode. Junos configuration then proceeds through the
container's own CLI exactly as on a vSRX, with the CLI-surface gaps noted
below.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 23d ago First seen · 583 lines · 177 tokens per session scan A 3380e91c4db2
csrx-proxmox-deploy is a skill published in the GitHub repository fastrevmd-lab/fwskillsshare (9 stars, last pushed 19d ago), licensed MIT. It adds 177 tokens to every session and 8,145 once invoked, about $0.0007 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-09-24.
Other skills, from other repositories
meraki-security-appliance
Cisco Meraki MX security appliance (read-only) — L3/L7 firewall rules, content filtering, IDS/IPS and AMP settings, site-to-site VPN, traffic shaping via Cisco's official Meraki MCP. Use when auditing Meraki firewall rules, reviewing content filtering, or inspecting MX VPN configuration.
live-demo
Add temporary, isolated hosted sessions to a tested robotics application.
edge-computing-expert
Design and implement production-grade edge computing solutions including CDN optimization, fog computing architectures, and distributed edge workloads. Use when the user mentions edge computing, CDN or edge caching, fog computing, MEC, IoT edge workloads, or latency-sensitive distributed deployments.
Infrastructure Development
Enterprise infrastructure patterns for AWS VPC, ECS, and PrivateLink deployments.
mk8s-byok
Runs workloads on your own hardware and provisions managed Kubernetes (mk8s) clusters on Control Plane. Use when the user asks about bare metal, on-prem, data centers, their own servers, mk8s, BYOK, or node pools.
proxmox-engineer
Proxmox VE e PBS — cluster, quorum, Ceph, LXC, VM, HA, replicação, storage e backup. Use quando o usuário disser "proxmox", "PVE", "ceph", "LXC", "container LXC", "VM não sobe", "cluster sem quorum", "PBS", "backup da VM". Sem MCP nem CLI padrão instalada — opera via SSH no nó ou API REST.