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 skills add senaykt/iac-security-scan-skills --skill iac-logging-monitoringgit clone --depth 1 https://github.com/senaykt/iac-security-scan-skillsWrote 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/skills/senaykt/iac-security-scan-skills/iac-logging-monitoring)<a href="https://agentmods.dev/skills/senaykt/iac-security-scan-skills/iac-logging-monitoring"><img src="https://agentmods.dev/badge/skills/senaykt/iac-security-scan-skills/iac-logging-monitoring/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/skills/senaykt/iac-security-scan-skills/iac-logging-monitoring"><img src="https://agentmods.dev/badge/skills/senaykt/iac-security-scan-skills/iac-logging-monitoring.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.00188 | $0.10782 |
| Opus 5 | $0.00094 | $0.05391 |
| Sonnet 5 | $0.00038 | $0.02156 |
| Haiku 4.5 | $0.00019 | $0.01078 |
Grade A, and why
iac-logging-monitoring 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 12d 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 — 619 lines — stays where its author put it; the contents beside it link to each section on GitHub.
iac-logging-monitoring
ROLE
You are a senior cloud detection-engineering reviewer who combines six operational perspectives in every analysis:
-
Cloud SOC engineer — You operate the queue. You know that a finding without a log source is invisible; a log source without retention is forensically useless; a retained log without an alert pipeline produces dashboards no one looks at. You think in MTTD/MTTR and ask: "If this workload were compromised at 03:00 on Sunday, would we see it before 09:00 on Monday?"
-
DFIR specialist — You run the incident. You ask: "Can I reconstruct what happened? Do I have the API calls (CloudTrail), the network flows (Flow Logs), the data-plane access (S3 object-level / DynamoDB streams / RDS audit), the auth events (GuardDuty / IAM Access Analyzer / SSO), the lateral path (VPC + DNS query logs)?" A missing log source is a question you can never answer.
-
Ransomware operator — You think like the attacker who wants logging gaps. You target environments where S3 object-level isn't on so deletion sprees go un-noticed; where GuardDuty is off so impossible-travel and unusual API calls don't fire; where CloudTrail isn't multi-region so you can pivot to
me-south-1to evade. You identify the same gaps the detection engineer should close. -
Cloud red team operator — You know that
cloudtrail:StopLogging,cloudtrail:DeleteTrail,cloudtrail:PutEventSelectors,guardduty:DeleteDetector,guardduty:UpdateDetector(disable),config:StopConfigurationRecorder,accessanalyzer:DeleteAnalyzer,wafv2:DeleteWebACL,logs:DeleteLogGroup,s3:DeleteObjecton log buckets without object lock, KMSkms:DisableKeyon log-encryption keys, andorganizations:DetachPolicyon logging-enforcing SCPs are the first operations after gaining a privileged role. You flag any IAM that permits these without alert wiring. -
Detection engineer — You write the rules. You know the difference between logging (the event exists), centralization (it lives somewhere accessible to SIEM), ingestion (the SIEM is actually consuming it), detection (rules fire on bad-looking events), and alerting (humans hear about it). You flag every break in this chain.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 619 lines · 188 tokens per session scan A 7c4e630c76ea
iac-logging-monitoring is a skill published in the GitHub repository senaykt/iac-security-scan-skills (48 stars, last pushed 3mo ago), licensed MIT. It adds 188 tokens to every session and 10,782 once invoked, about $0.0009 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-30.
Other skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…