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 skills/automateyournetwork/netclaw/checkpointnpx skills add automateyournetwork/netclaw --skill checkpointgit clone --depth 1 https://github.com/automateyournetwork/netclawWrote 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/automateyournetwork/netclaw/checkpoint)<a href="https://agentmods.dev/skills/automateyournetwork/netclaw/checkpoint"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/checkpoint.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 | $0.00000 | $0.02290 |
| Opus 5 | $0.00000 | $0.01145 |
| Sonnet 5 | $0.00000 | $0.00458 |
| Haiku 4.5 | $0.00000 | $0.00229 |
Grade A, and why
checkpoint 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 — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check Point Security Platform
A comprehensive skill for interacting with Check Point enterprise security infrastructure through 15 MCP servers.
Activation
This skill activates when user queries involve:
- Check Point firewall policies, rules, or objects
- Security policy auditing or compliance
- Threat intelligence (IP/URL/file reputation)
- Gateway diagnostics and troubleshooting
- SASE management and cloud security
- Threat prevention profiles and IPS
- Malware analysis and file sandboxing
- Check Point documentation queries
Explicit activation: /checkpoint prefix
MCP Servers
This skill composes across 15 Check Point MCP servers:
| Server | Purpose | Credentials |
|---|---|---|
chkp-management |
Policies, rules, objects, topology | MGMT server |
chkp-management-logs |
Connection and audit logs | MGMT server |
chkp-threat-prevention |
TP profiles, IPS, IOC feeds | MGMT server |
chkp-https-inspection |
HTTPS inspection policies | MGMT server |
chkp-harmony-sase |
SASE regions, applications | SASE API |
chkp-reputation-service |
IP/URL/file reputation | Reputation API |
chkp-quantum-gw-cli |
Gateway diagnostics | MGMT server |
chkp-gw-connection-analysis |
Connection debugging | MGMT server |
chkp-threat-emulation |
Malware analysis | TE API |
chkp-quantum-gaia |
GAIA OS management | MGMT server |
chkp-documentation |
Check Point docs search | None |
chkp-spark-management |
Spark firewall (MSP) | Spark API |
chkp-cpinfo-analysis |
CPInfo diagnostics | None |
chkp-argos-erm |
Exposure/risk management | Argos API |
chkp-policy-insights |
Policy optimization | MGMT server |
Query Routing
Policy & Object Queries (US1)
Keywords: policy, rule, firewall, access, NAT, object, host, network, group, audit, permissive, compliance
MCP: chkp-management, chkp-policy-insights
Examples:
- "show me all firewall policies"
- "audit my policies for overly permissive rules"
- "show all rules allowing any-any"
- "list host objects matching 10.1.*"
- "show NAT rules for the DMZ policy"
- "suggest policy optimizations"
- "show gateways and servers"
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 · 289 lines · 0 tokens per session scan A a88bf2dbc050
checkpoint is a skill published in the GitHub repository automateyournetwork/netclaw (650 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,290 tokens. 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…