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/HermeticOrmus/LibreSecOps-Claude-CodeWrote 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/hermeticormus/libresecops-claude-code/gcp-sec-audit)<a href="https://agentmods.dev/commands/hermeticormus/libresecops-claude-code/gcp-sec-audit"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/gcp-sec-audit.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.1 | $0.00000 | $0.01165 |
| Opus 5 | $0.00000 | $0.00583 |
| Sonnet 5 | $0.00000 | $0.00233 |
| Haiku 4.5 | $0.00000 | $0.00117 |
Grade A, and why
gcp-sec-audit 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 6d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/gcp-sec-audit
Structured security audit of GCP configuration covering IAM, GCS, VPC, Cloud Audit Logs, and Organization Policies.
Trigger
Use when you need to:
- Review GCP project or organization configuration for security gaps
- Audit Terraform configurations targeting GCP before deployment
- Validate Organization Policy constraints and IAM bindings
- Prepare for a CIS GCP Foundations Benchmark assessment
- Investigate GCP security posture after organizational changes
Input
One of:
- Live environment:
gcloudCLI authenticated with Viewer role at project or organization level - Infrastructure-as-code: Terraform files (
.tf) using the Google provider - Configuration export: Output from
gcloudcommands, Security Command Center findings, ScoutSuite reports - Specific scope: Focus area (e.g., "IAM only", "networking", "Cloud SQL")
Process
Phase 1: Identity & Access Management
-
Service account hygiene
- Service accounts with keys (
gcloud iam service-accounts keys list --iam-account=SA_EMAIL) - Default service accounts in use ([email protected])
- Service accounts with basic roles (Owner, Editor)
- User-managed service account key rotation (keys older than 90 days)
- Service account impersonation chains
- Service accounts with keys (
-
IAM bindings
- Basic roles (Owner/Editor/Viewer) assigned to any principal
allUsersorallAuthenticatedUsersin any IAM binding- IAM bindings at organization/folder level (high blast radius)
- Separation of duties (same principal with conflicting roles)
- Domain-restricted sharing (
constraints/iam.allowedPolicyMemberDomains)
-
Workload Identity
- External workloads using service account keys vs Workload Identity Federation
- GKE workloads using node-level SA vs Workload Identity
Phase 2: Storage Security
- Cloud Storage (GCS)
- Uniform bucket-level access enforced (
gcloud storage buckets describe gs://BUCKET) - Public buckets (
allUsersorallAuthenticatedUsersin bucket IAM) - Bucket-level CMEK encryption
- Retention policies on critical buckets
- Access logging enabled
- Uniform bucket-level access enforced (
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.
- 6d ago First seen · 138 lines · 0 tokens per session scan A 6999eef9f929
gcp-sec-audit is a command published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,165 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-31.
Other commands, from other repositories
build-agent
Build an AI agent on Cloudflare using the Agents SDK.
build-mcp
Build a remote MCP server on Cloudflare using McpAgent.
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.