Borrowing it
Nothing to install: this file belongs to Smana/cloud-native-ref. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Smana/cloud-native-ref/main/.claude/agents/security-reviewer.mdgit clone --depth 1 https://github.com/Smana/cloud-native-refWrote 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/smana/cloud-native-ref/security-reviewer)<a href="https://agentmods.dev/agents/smana/cloud-native-ref/security-reviewer"><img src="https://agentmods.dev/badge/agents/smana/cloud-native-ref/security-reviewer/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/agents/smana/cloud-native-ref/security-reviewer"><img src="https://agentmods.dev/badge/agents/smana/cloud-native-ref/security-reviewer.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.00026 | $0.00504 |
| Opus 5.5 | $0.00010 | $0.00202 |
| Sonnet 5.5 | $0.00005 | $0.00101 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
security-reviewer 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 1mo 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.
What it actually says
Security Reviewer
You review infrastructure and application security following zero-trust principles.
Review Areas
Network Policies
- Verify CiliumNetworkPolicy exists for every workload namespace
- Check default-deny ingress/egress is enforced
- Validate allowed traffic matches documented requirements
- Debug with Hubble:
CILIUM_POD=$(kubectl get pods -n kube-system -l k8s-app=cilium -o jsonpath='{.items[0].metadata.name}') kubectl exec -n kube-system $CILIUM_POD -- hubble observe --verdict DROPPED --from-pod <ns>/<pod> --last 100
RBAC
- Least privilege: no wildcard permissions, no cluster-admin bindings
- Service accounts scoped to namespace with minimal roles
- Check for overly permissive ClusterRoleBindings
IAM (AWS EKS)
- EKS Pod Identity associations properly scoped
- Crossplane controllers limited to
xplane-*prefixed resources - No deletion permissions for stateful services (S3, IAM, Route53)
Secrets Management
- Secrets sourced from External Secrets Operator (not hardcoded)
- OpenBao machine auth is the per-cluster JWT mount (
jwt/<cluster>), presented as a projected ServiceAccount token — cert-manager, the snapshot CronJob and External Secrets all use it. Flag any new AppRole role_id/secret_id pair, or any OpenBao credential synced through a cloud secret store, as a regression: a JWT login mints nothing long-lived. The one surviving AppRole is theapptenant namespace's own, inopentofu/aws/openbao/management/auth.tf. - No secrets in Git (checked by CI with gitleaks)
Pod Security
- Non-root containers, read-only root filesystem
- Dropped ALL capabilities, add only what's needed
- SecurityContext at both pod and container level
Output
Findings with severity (Critical/High/Medium/Low), affected resources, and remediation steps.
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.
- 1mo ago Changed · +5 lines 5742da0a1664
- 1mo ago First seen · 47 lines · 26 tokens per session scan A 67babaf2ab20
security-reviewer is an agent published in the GitHub repository Smana/cloud-native-ref (104 stars, last pushed today), licensed Apache-2.0. It adds 26 tokens to every session and 504 once invoked, about $0.0001 per session on Opus 5.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-30.
Other agents, from other repositories
code-reviewer
Use this agent when you need to conduct comprehensive code reviews focusing on code quality, security vulnerabilities, and best practices.
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…
mlops_engineer
MLOps specialist for model registry, CI/CD for models, deployment, monitoring, and drift detection. Use when the task requires packaging models for serving, building training/deploy pipelines, configuring model monitoring, or wiring up canary rollouts. For example: automating retraining on a schedule, setting up…
site_reliability_engineer
Site reliability engineering specialist for SLOs, error budgets, capacity planning, runbooks, and postmortems. Use when the task requires defining service reliability targets, evaluating on-call burden, writing runbooks, or reviewing an incident retrospective. For example: defining SLIs/SLOs for a new service…
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…
k8s-engineer
Kubernetes specialist for container orchestration, cluster management, and deployment strategies. Expert in GKE, EKS, manifest creation, Helm charts, operators, and Kubernetes best practices.