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/commands/trumb/claude-nginx-hardening/rollback-nginx)<a href="https://agentmods.dev/commands/trumb/claude-nginx-hardening/rollback-nginx"><img src="https://agentmods.dev/badge/commands/trumb/claude-nginx-hardening/rollback-nginx/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/commands/trumb/claude-nginx-hardening/rollback-nginx"><img src="https://agentmods.dev/badge/commands/trumb/claude-nginx-hardening/rollback-nginx.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.00016 | $0.00518 |
| Opus 5 | $0.00008 | $0.00259 |
| Sonnet 5 | $0.00003 | $0.00104 |
| Haiku 4.5 | $0.00002 | $0.00052 |
Grade B, and why
rollback-nginx scanned grade B 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 9d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
6. **Validate** — `sudo nginx -t` What it actually says
Context
- Current config: !
ls /etc/nginx/snippets/security-hardening.conf 2>/dev/null && echo "PRESENT" || echo "MISSING" - Available backups: !
ls /etc/nginx/snippets/security-hardening.conf.bak.* 2>/dev/null | wc -lbackups found - Latest backup: !
ls -t /etc/nginx/snippets/security-hardening.conf.bak.* 2>/dev/null | head -1 || echo "none"
Operating Mode
DEFAULT: R0 + R1 (preview only)
With --apply: W1 (local restore)
With --remote: W1 + X1 (local + remote restore)
Read @skills/nginx-hardening/EXECUTION-POLICY.md for full policy.
Subcommands
/harden-nginx rollback (bare)
Interactive mode — list recent backups and let user choose.
/harden-nginx rollback latest
Preview what would change if restoring the most recent backup.
With --apply: actually restore it.
/harden-nginx rollback <backup-id>
Preview what would change if restoring a specific backup.
With --apply: actually restore it.
/harden-nginx rollback --list
Show all available backups with timestamps, sizes, and run IDs.
Workflow
- List backups —
python3 scripts/rollback-manager.py list --file <target> - Preview —
python3 scripts/rollback-manager.py preview --file <target> --backup-id <id>Show unified diff to user - Confirm — User must explicitly approve restore
- Safety backup — Create backup of CURRENT state before restoring (so restore is reversible)
- Restore —
python3 scripts/rollback-manager.py restore --file <target> --backup-id <id> - Validate —
sudo nginx -t - Reload —
sudo systemctl reload nginx - Git — Optionally create revert commit (NO force push, NO hard reset — Invariant 11)
- Log — Append rollback record to CHANGELOG.md
On failure at step 6 or 7:
- Restore from the safety backup created in step 4
- Run nginx -t again to verify recovery
- Report failure, recommend manual investigation
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.
- 9d ago First seen · 52 lines · 16 tokens per session scan B 3e212225247f
rollback-nginx is a command published in the GitHub repository trumb/claude-nginx-hardening (2 stars, last pushed 5mo ago), licensed MIT. It adds 16 tokens to every session and 518 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.