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 oborchers/fractional-cto --skill security-monitoring-from-day-onegit clone --depth 1 https://github.com/oborchers/fractional-ctoWrote 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/oborchers/fractional-cto/security-monitoring-from-day-one)<a href="https://agentmods.dev/skills/oborchers/fractional-cto/security-monitoring-from-day-one"><img src="https://agentmods.dev/badge/skills/oborchers/fractional-cto/security-monitoring-from-day-one/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/oborchers/fractional-cto/security-monitoring-from-day-one"><img src="https://agentmods.dev/badge/skills/oborchers/fractional-cto/security-monitoring-from-day-one.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00100 | $0.02168 |
| Opus 5 | $0.00050 | $0.01084 |
| Sonnet 5 | $0.00020 | $0.00434 |
| Haiku 4.5 | $0.00010 | $0.00217 |
Grade A, and why
security-monitoring-from-day-one 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Monitoring Deploys in Week 2, Not After the Breach
Security monitoring is not a feature you add when the compliance audit arrives. It ships alongside the infrastructure -- in week 2, right after account structure and networking. Every week without monitoring is a week where threats go undetected, misconfigurations accumulate silently, and vulnerabilities sit in production unscanned. The cost of enabling managed security services on day one is trivial. The cost of discovering six months of unmonitored exposure is catastrophic.
Start with managed security services. Do not build a custom SIEM. Do not cobble together open-source tools. Use the cloud provider's native threat detection, compliance scanning, and vulnerability assessment. These services integrate with each other, aggregate findings centrally, and require no infrastructure to operate. You can always add third-party tools later -- but you cannot retroactively detect last month's intrusion.
Week 2 means enabling the managed services with default settings -- not tuning every rule. Turn on threat detection and basic configuration auditing. The full compliance framework and workload-specific scanning comes later as you understand your baseline. The landing zone tooling (see multi-account-from-day-one skill) handles the account structure and guardrails; this skill covers the security services you enable on top of that foundation.
The Four Security Pillars
Every cloud foundation needs four categories of security monitoring deployed from the start. Each pillar answers a different question.
| Pillar | Question It Answers | What It Detects |
|---|---|---|
| Threat Detection | Is someone attacking us right now? | Unauthorized API calls, compromised credentials, cryptocurrency mining, port scanning, data exfiltration |
| Compliance Scanning | Do our resources meet security standards? | CIS benchmark violations, industry framework gaps, security best practice deviations |
| Vulnerability Scanning | Do our workloads have known weaknesses? | CVEs in container images, OS packages, application dependencies, network reachability issues |
| Configuration Auditing | Are resources configured safely? | Unencrypted storage, public access, missing logging, overly permissive IAM, security group misconfigurations |
What ships with it
2 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 · 154 lines · 100 tokens per session scan A 6bf333f3e3ed
security-monitoring-from-day-one is a skill published in the GitHub repository oborchers/fractional-cto (30 stars, last pushed 1mo ago), licensed MIT. It adds 100 tokens to every session and 2,168 once invoked, about $0.0005 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…