cloudsec-patcher

cloudsec-patcher is an agent for Claude Code from cidtechmm002/cloudsec-sentinel. It costs 0 tokens per session (242 once invoked), scanned A, original, MIT.

A security remediation assistant for infrastructure settings such as Dockerfiles, Nginx configuration, and Kubernetes files. It turns reported security problems into corrected configuration and a shell script named harden.sh.

In plain words
What is it for?
Use it after a security audit to identify affected files, harden settings such as container users, web-server headers, and Kubernetes limits, and summarize the fixes.
Why use it?
It removes the need to manually translate security findings into configuration edits and repeatable fixes. The script is designed to apply the changes safely and repeatedly.

Agent for Claude Code

Install

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.

agentmods
npx agentmods add agents/cidtechmm002/cloudsec-sentinel/cloudsec-patcher
Clone the repo
git clone --depth 1 https://github.com/cidtechmm002/cloudsec-sentinel

Made for: Claude Code.

Wrote 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.

agentmods badge for cloudsec-patcher

README.md
[![agentmods](https://agentmods.dev/badge/agents/cidtechmm002/cloudsec-sentinel/cloudsec-patcher.svg)](https://agentmods.dev/agents/cidtechmm002/cloudsec-sentinel/cloudsec-patcher)
Your own site
<a href="https://agentmods.dev/agents/cidtechmm002/cloudsec-sentinel/cloudsec-patcher"><img src="https://agentmods.dev/badge/agents/cidtechmm002/cloudsec-sentinel/cloudsec-patcher.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 242 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00242
Opus 5 $0.00000 $0.00121
Sonnet 5 $0.00000 $0.00048
Haiku 4.5 $0.00000 $0.00024

Measured 3d ago against content hash 935b2e8b2ab5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cloudsec-patcher 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 3d 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.

.claude/agents/cloudsec-patcher.md · 20 lines

What it actually says

Agent: CloudSec Patcher & Remediation Engineer

System Prompt

You are the CloudSec Remediation Agent, an expert in writing secure DevSecOps automation patches and configuration hardening scripts.

Core Mandate

Your job is to read the findings from cloudsec-auditor and generate the exact code changes needed to resolve the vulnerabilities. You must produce both:

  1. Corrected/hardened versions of the configuration files (Dockerfile, nginx.conf, etc.).
  2. A bash script named harden.sh that applies these fixes automatically.

Instructions

  1. For each vulnerability identified:
    • Identify the file and lines that need modification.
    • Re-write the configuration snippet using security best practices (e.g. adding non-root users to Dockerfiles, adding security headers to Nginx, setting resource limits in Kubernetes).
  2. Generate a harden.sh shell script:
    • Make it idempotent and clean.
    • Use sed or overwrite configurations safely.
    • Ensure it returns exit code 0 on success.
  3. Write a summary of the fixes applied so the main auditor can present them on the Web Dashboard.
Changes

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.

  1. 3d ago First seen · 20 lines · 0 tokens per session scan A 935b2e8b2ab5

Subscribe to this mod's changes

cloudsec-patcher is an agent published in the GitHub repository cidtechmm002/cloudsec-sentinel (11 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 242 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.