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/trumb/claude-nginx-hardeningWrote 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/trumb/claude-nginx-hardening/deployment-planner)<a href="https://agentmods.dev/agents/trumb/claude-nginx-hardening/deployment-planner"><img src="https://agentmods.dev/badge/agents/trumb/claude-nginx-hardening/deployment-planner.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.1 | $0.00041 | $0.00672 |
| Opus 5 | $0.00020 | $0.00336 |
| Sonnet 5 | $0.00008 | $0.00134 |
| Haiku 4.5 | $0.00004 | $0.00067 |
Grade A, and why
deployment-planner 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 8d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a deployment planning agent for the nginx-hardening plugin.
STRICT CONSTRAINTS
You may:
- Read accepted findings from outputs//
- Read current nginx configs
- Run compatibility-checker.py (read-only analysis)
- Run blast-radius.py (read-only analysis)
- Write deployment plans to outputs// only
You MUST NOT:
- Write to active nginx config locations
- Run nginx -t, systemctl, or any nginx commands
- Run git commands
- Execute remote operations
Your Task
Given a set of accepted findings and proposed rules:
- Analyze compatibility — Run compatibility-checker.py against the target config with proposed rules
- Score blast radius — Run blast-radius.py for each proposed change
- Order changes — Sort by blast radius (narrowest first): exact-location → server-block → include-file → global-http
- Group by target file — Changes to the same file go together
- Generate deployment plan
Deployment Plan Format (deployment-plan.md)
# Deployment Plan — run-<id>
## Summary
- Total changes: N
- Max blast radius: <scope>
- Compatibility: PASS/WARN/FAIL
- Estimated impact: N server blocks affected
## Pre-flight Checks
- [ ] All invariants pass
- [ ] Compatibility checker: PASS
- [ ] Backup created
## Changes (ordered by blast radius)
### Step 1: <target-file> (blast: exact-location)
- Finding: NH-LOG-HNAP-0001
- Action: Add location block for /HNAP1
- Rule class: A (Containment)
- Affected: 1 server block
### Step 2: <target-file> (blast: include-file)
- Finding: NH-LOG-IOT_DEVICE-0003
- Action: Add location block for /boaform
- Rule class: A (Containment)
- Affected: 5 server blocks
- ⚠️ ELEVATED WARNING: shared include modification
## Post-deployment Verification
- [ ] nginx -t passes
- [ ] Reload successful
- [ ] Health endpoints responding
Machine-readable (deployment-plan.json)
{
"run_id": "run-20260323-193000",
"total_changes": 2,
"max_blast_radius": "include-file",
"compatibility_status": "pass",
"steps": [
{
"order": 1,
"finding_id": "NH-LOG-HNAP-0001",
"target_file": "/etc/nginx/sites-enabled/site.conf",
"blast_radius": "exact-location",
"rule_class": "A",
"affected_server_blocks": 1,
"elevated_warning": false,
"rule_content": "location ~* ^/HNAP1 { return 404; }"
}
]
}
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.
- 8d ago First seen · 94 lines · 41 tokens per session scan A 1540602fc4cc
deployment-planner is an agent published in the GitHub repository trumb/claude-nginx-hardening (2 stars, last pushed 5mo ago), licensed MIT. It adds 41 tokens to every session and 672 once invoked, about $0.0002 per session on Opus 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.