remediator

remediator is an agent for Claude Code from prajapatimehul/comp-agent. It costs 39 tokens per session (1,837 once invoked), scanned A, original, MIT.

An agent for fixing AWS compliance findings identified by a scanner. It gathers before-and-after evidence, explains the related SOC 2 or HIPAA controls, proposes a fix with risk information, and waits for human approval.

In plain words
What is it for?
Use it to process findings stored in the project’s compliance files, research their control context, propose remediation, capture evidence, and verify the result with a Prowler rescan.
Why use it?
It provides a controlled path from an open finding to a verified correction without applying changes silently.

Agent for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Part of the compliance-pilot plugin — 4 skills, 3 agents, 1 hook, 1 MCP server shipped together

Good fit Use it to process findings stored in the project’s compliance files, research their control context, propose remediation, capture evidence, and verify the result with a Prowler rescan.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/prajapatimehul/comp-agent/remediator
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.

Clone the repo
git clone --depth 1 https://github.com/prajapatimehul/comp-agent

Made for: Claude Code.

Or install compliance-pilot, the plugin that ships this one along with the rest of its 4 skills, 3 agents, 1 hook, 1 MCP server.

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 remediator

README.md
[![agentmods](https://agentmods.dev/badge/agents/prajapatimehul/comp-agent/remediator.svg)](https://agentmods.dev/agents/prajapatimehul/comp-agent/remediator)
Your own site
<a href="https://agentmods.dev/agents/prajapatimehul/comp-agent/remediator"><img src="https://agentmods.dev/badge/agents/prajapatimehul/comp-agent/remediator.svg" alt="Measured on agentmods" height="20"></a>
Per session 39 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,837 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00039 $0.01837
Opus 5 $0.00019 $0.00919
Sonnet 5 $0.00008 $0.00367
Haiku 4.5 $0.00004 $0.00184

Measured 8d ago against content hash b8c16d7b549d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

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

agents/remediator.md · 233 lines

How it starts

The opening of the file, as written. The whole thing — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Remediator Agent

You are the compliance remediator. You fix AWS misconfigurations identified by the scanner, with full evidence capture and human approval.

Tools Available

Bash, Read, Write, Edit, Glob, Grep

Inputs

You receive a finding ID or path via $ARGUMENTS. Read the finding JSON from .compliance/findings/.

Workflow

For each finding you are assigned:

1. Read the Finding

Load the finding JSON. Verify status is open or in_progress. If already verified or skipped, skip it.

Update the finding status to in_progress.

2. Look Up Compliance Context

Read the relevant rules from rules/soc2.md and rules/hipaa.md to understand which controls this finding maps to and why it matters.

Also consult the knowledge base in knowledge/:

  • requirements-soc2.json / requirements-hipaa.json — get the full requirement description for the mapped controls
  • policies.json + relations.json — identify which organizational policies are relevant to this finding
  • tasks.json + relations.json — find recommended evidence collection tasks for the control being remediated

Use this context to provide richer explanations in the fix proposal (step 4).

3. Capture Before-State Evidence

Create the evidence directory:

mkdir -p .compliance/evidence/{finding-id}

Run the appropriate aws describe/get command for the resource and save the output:

aws {service} describe-{resource-type} ... > .compliance/evidence/{finding-id}/before.json

Common before-state commands by service:

  • S3 encryption: aws s3api get-bucket-encryption --bucket BUCKET
  • S3 public access: aws s3api get-public-access-block --bucket BUCKET
  • S3 logging: aws s3api get-bucket-logging --bucket BUCKET
  • S3 policy: aws s3api get-bucket-policy --bucket BUCKET
  • RDS encryption: aws rds describe-db-instances --db-instance-identifier ID
  • RDS public: aws rds describe-db-instances --db-instance-identifier ID
  • EC2 SG: aws ec2 describe-security-groups --group-ids SG-ID
  • EC2 EBS: aws ec2 describe-volumes --volume-ids VOL-ID
  • IAM policy: aws iam get-policy --policy-arn ARN
  • IAM MFA: aws iam list-mfa-devices --user-name USER
  • CloudTrail: aws cloudtrail describe-trails
  • VPC flow logs: aws ec2 describe-flow-logs --filter "Name=resource-id,Values=VPC-ID"
  • KMS rotation: aws kms get-key-rotation-status --key-id KEY-ID
  • Config: aws configservice describe-configuration-recorders

Read the full file on GitHub · 233 lines

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. 8d ago First seen · 233 lines · 39 tokens per session scan A b8c16d7b549d

Subscribe to this mod's changes

remediator is an agent published in the GitHub repository prajapatimehul/comp-agent (5 stars, last pushed 6mo ago), licensed MIT. It adds 39 tokens to every session and 1,837 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.

Related

Other agents, from other repositories

aws-architecture-review-expert

Provides expert AWS architecture and CloudFormation review capabilities specializing in Well-Architected Framework compliance, security best practices, cost optimization, and IaC quality. Validates AWS architectures and CloudFormation templates for scalability, reliability, and operational excellence. Use PROACTIVELY…

giuseppe-trisciuoglio/developer-kit · 76 tokens

azure-architect

Designs Azure cloud architecture, optimizes costs, and implements security best practices. Use when designing Azure infrastructure, selecting Azure services, or optimizing Azure deployments.

armanzeroeight/fastagent-plugins · 35 tokens

database-migration

Database migration and modernization specialist. USE FOR: planning database migrations, designing migration strategies, validating data integrity. DO NOT USE FOR: operational database management, routine backups.

ivegamsft/basecoat · 37 tokens

deployment-verifier

Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.

asysta-act/agent-flow · 24 tokens

llm2bedrock-report-generator

Synthesize all prior phase results into a final Markdown migration report — model mapping, eval scores, code diffs, cost comparison, next steps. Writes MIGRATIONREPORT .md and returns a structured report object.

awslabs/startups · 52 tokens

staff-sre

Production reliability specialist. Use PROACTIVELY for incident response, production readiness reviews, SLO enforcement, capacity planning, and any production concern. First responder for incidents.

caiaffa/claude-code-ultimate-engineering-system · 38 tokens