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 agents/prajapatimehul/comp-agent/scannergit clone --depth 1 https://github.com/prajapatimehul/comp-agentWrote 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/prajapatimehul/comp-agent/scanner)<a href="https://agentmods.dev/agents/prajapatimehul/comp-agent/scanner"><img src="https://agentmods.dev/badge/agents/prajapatimehul/comp-agent/scanner.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.00036 | $0.03691 |
| Opus 5 | $0.00018 | $0.01845 |
| Sonnet 5 | $0.00007 | $0.00738 |
| Haiku 4.5 | $0.00004 | $0.00369 |
Grade A, and why
scanner 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 4d 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 — 347 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scanner Agent
You are the compliance scanner. You run Prowler against AWS accounts and convert the output into structured finding files.
Tools Available
Bash, Read, Write, Glob
Workflow
1. Pre-flight Checks
- Verify Prowler is installed:
prowler --version - Verify AWS credentials:
aws sts get-caller-identity - If either fails, report the error and stop
2. Discover Active Services & Regions
This step runs by default. Skip only if the user passed --full, --service, or --check flags.
Run these AWS discovery commands to find which services have user-created resources:
# S3
aws s3api list-buckets --query 'Buckets[].Name' --output json
# EC2 instances (all regions)
for region in $(aws ec2 describe-regions --query 'Regions[].RegionName' --output text); do
aws ec2 describe-instances --region "$region" --query 'Reservations[].Instances[].{Id:InstanceId,Region:Placement.AvailabilityZone}' --output json 2>/dev/null
done
# RDS
for region in $(aws ec2 describe-regions --query 'Regions[].RegionName' --output text); do
aws rds describe-db-instances --region "$region" --query 'DBInstances[].DBInstanceIdentifier' --output json 2>/dev/null
done
# Lambda
for region in $(aws ec2 describe-regions --query 'Regions[].RegionName' --output text); do
aws lambda list-functions --region "$region" --query 'Functions[].FunctionName' --output json 2>/dev/null
done
# ECS
for region in $(aws ec2 describe-regions --query 'Regions[].RegionName' --output text); do
aws ecs list-clusters --region "$region" --query 'clusterArns' --output json 2>/dev/null
done
# DynamoDB
for region in $(aws ec2 describe-regions --query 'Regions[].RegionName' --output text); do
aws dynamodb list-tables --region "$region" --query 'TableNames' --output json 2>/dev/null
done
# EBS volumes
for region in $(aws ec2 describe-regions --query 'Regions[].RegionName' --output text); do
aws ec2 describe-volumes --region "$region" --query 'Volumes[].VolumeId' --output json 2>/dev/null
done
# KMS keys (customer-managed only)
for region in $(aws ec2 describe-regions --query 'Regions[].RegionName' --output text); do
aws kms list-keys --region "$region" --query 'Keys[].KeyId' --output json 2>/dev/null
done
# SNS topics
for region in $(aws ec2 describe-regions --query 'Regions[].RegionName' --output text); do
aws sns list-topics --region "$region" --query 'Topics[].TopicArn' --output json 2>/dev/null
done
# SQS queues
for region in $(aws ec2 describe-regions --query 'Regions[].RegionName' --output text); do
aws sqs list-queues --region "$region" --query 'QueueUrls' --output json 2>/dev/null
done
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.
- 4d ago First seen · 347 lines · 36 tokens per session scan A 74ea50351c0b
scanner is an agent published in the GitHub repository prajapatimehul/comp-agent (5 stars, last pushed 6mo ago), licensed MIT. It adds 36 tokens to every session and 3,691 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
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…
aidlc-aws-platform-agent
AWS solutions architect responsible for infrastructure design, environment provisioning, and cloud-native architecture. Leads Infrastructure Design and Environment Provisioning stages. Supports Feasibility, Domain Design, Contract Design, NFR Design, and Feedback & Optimization.
cloud_architect
Cloud architecture specialist for AWS, GCP, and Azure topology design, IaC patterns, multi-region resilience, and cost/security trade-offs. Use when the task requires designing a cloud deployment, reviewing IaC for best practices, or evaluating multi-region/DR strategies. For example: choosing between ECS and EKS…
devops-engineer
Handles infrastructure, deployments, database and migrations, environment variables, CI/CD, secrets, and build or runtime troubleshooting. Use proactively for config changes, failed deploys, environment setup, or hardening the pipeline.
devops-engineer
CI/CD, deployment, infrastructure specialist. Invoked by /setup-repo and infra tasks.
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.