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 srx-ipsgit 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/srx-ips)<a href="https://agentmods.dev/skills/fastrevmd-lab/fwskillsshare/srx-ips"><img src="https://agentmods.dev/badge/skills/fastrevmd-lab/fwskillsshare/srx-ips/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/srx-ips"><img src="https://agentmods.dev/badge/skills/fastrevmd-lab/fwskillsshare/srx-ips.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.00136 | $0.07318 |
| Opus 5.5 | $0.00054 | $0.02927 |
| Sonnet 5.5 | $0.00027 | $0.01464 |
| Haiku 4.5 | $0.00014 | $0.00732 |
Grade A, and why
srx-ips 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 22d 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 — 553 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SRX IPS Management
STATUS: draft (v0.1.0). Contributed by Javier Grizzuti (@jgrizzuti) from lab work against Juniper's junos-mcp-server, then revised against Juniper documentation. Items marked [unverified] have not yet been checked on a vSRX and must not be relied on until they are. Values in
<angle brackets>are site-specific.Partial validation performed on vSRX 26.2R1.7 (attack database 3929) on 2026-09-23: commit check behavior, predefined-attack browsing, and signature syntax requirements were verified on hardware.
Overview
This skill covers the complete IPS lifecycle (Junos calls the feature IDP) on Juniper SRX platforms:
Triage reads what an SRX's IDP policy and logs actually show, turns that
into a plain-language finding, and proposes one specific, reviewable change that
moves relevant monitor-mode (no-action) rules to enforcement. Use this
workflow when reviewing IDP or screen logs, checking whether attacks were
blocked, investigating suspicious traffic, or deciding which rules to enforce.
Custom signatures turn a specific finding — an exposed path, an injection
technique, an auth-bypass pattern — into a custom IPS signature that is checked
against existing coverage, validated without activation, proven in monitor mode,
and only then proposed for enforcement. Use this workflow when a scanner or
pentest finding needs IPS detection, when writing a custom-attack, or when
extending IPS coverage beyond the predefined database.
Nothing is changed on the device without explicit approval, and "yes" to an
analysis request is never approval to push configuration. Attack database
updates and IDP license maintenance belong to
srx-license-signature-maintenance.
Runtime intake
Before starting the workflow, inspect the request, supplied artifacts, and available approved read-only evidence. If unresolved facts could materially change safety, scope, correctness, confidence, or the requested output, read references/runtime-intake.md. For each unresolved material fact whose catalog condition is true, invoke Claude AskUserQuestion or Codex request_user_input before continuing or issuing an open-ended request. Ask at most three single-select catalog questions per round. After each response, ask another round whenever any unresolved material catalog condition remains true; continue only when none remain. Do not repeat answered questions or show the full catalog. Without a native tool, present each selected catalog question with its 2-3 labeled choices and a free-text Other path in concise plain text; do not substitute a generic checklist. Never request secrets or unredacted customer data. Treat intake answers as task context, not approval for a live change; obtain separate explicit approval before configuration, commit, upgrade, reboot, delete, or failover actions.
What ships with it
4 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.
- 22d ago Changed · +1 lines 49deffac436f
- 23d ago First seen · 552 lines · 136 tokens per session scan A 770d78c399aa
srx-ips is a skill published in the GitHub repository fastrevmd-lab/fwskillsshare (9 stars, last pushed 19d ago), licensed MIT. It adds 136 tokens to every session and 7,318 once invoked, about $0.0005 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.
radkit-remote-access
Cisco RADKit — cloud-relayed remote device access, CLI execution, SNMP polling, device inventory discovery, attribute inspection. Use when accessing remote network devices through a cloud relay, running CLI on air-gapped devices, polling SNMP metrics remotely, or discovering device inventory via RADKit.
fmc-firewall-ops
Cisco Secure Firewall FMC — access policy search, rule inspection, FTD device targeting, multi-FMC profile management. Use when searching firewall rules by IP or FQDN, checking if host A can reach host B through the firewall, auditing FMC access policies, or reviewing SGT-based segmentation rules.
fortianalyzer-ops
FortiAnalyzer log operations — policy-filtered traffic log query within a bounded time window, offset pagination, per-policy activity checks, and logging-device inventory. Use when asking whether traffic actually matched a firewall rule, investigating what hit a policy, or determining whether a rule is genuinely…
fortigate-ops
FortiGate device operations — system status, interfaces, routing, IPsec VPN tunnel state with phase 1 and phase 2 reported separately, HA member identification, per-VDOM scoping, and manager-vs-device drift detection. Use when asking what a FortiGate is ACTUALLY doing right now, whether a tunnel is up, or whether the…
fortimanager-ops
FortiManager policy operations — ADOM inventory, policy package review, recursive object resolution, revision history, install preview, and gated package install. Use when auditing FortiGate firewall policy at the MANAGER level (intent), reviewing ADOM policy packages, or planning a package install with rollback…