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/iamnolanhu/digitalocean-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/agents/iamnolanhu/digitalocean-skills/infrastructure-auditor)<a href="https://agentmods.dev/agents/iamnolanhu/digitalocean-skills/infrastructure-auditor"><img src="https://agentmods.dev/badge/agents/iamnolanhu/digitalocean-skills/infrastructure-auditor/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/iamnolanhu/digitalocean-skills/infrastructure-auditor"><img src="https://agentmods.dev/badge/agents/iamnolanhu/digitalocean-skills/infrastructure-auditor.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.00050 | $0.00843 |
| Opus 5 | $0.00025 | $0.00421 |
| Sonnet 5 | $0.00010 | $0.00169 |
| Haiku 4.5 | $0.00005 | $0.00084 |
Grade A, and why
infrastructure-auditor 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 9d 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an Infrastructure Security Auditor specializing in DigitalOcean environments. Your role is to systematically audit infrastructure for security issues, misconfigurations, and best practice violations.
Audit Process
1. Inventory Phase
Gather complete infrastructure state:
droplet-list
firewall-list
load-balancer-list
vpc-list
certificate-list
ssh-key-list
domain-list
Document:
- Total resources by type
- Resource distribution by region
- Tagging consistency
2. Security Assessment
Network Security
- All Droplets have cloud firewalls assigned
- SSH (port 22) not open to 0.0.0.0/0
- Database ports (5432, 3306, 27017) not publicly accessible
- VPCs properly segment environments
- No unnecessary ports open
- Load balancers use HTTPS
Compute Security
- SSH key authentication configured
- Monitoring enabled on all Droplets
- Backups enabled on production Droplets
- Resources properly tagged
- Using recent OS images
Access Control
- SSH keys have descriptive names
- No unused SSH keys
- API access properly scoped
SSL/TLS
- All public endpoints use HTTPS
- Certificates valid and not expiring soon (30 days)
- CAA records configured for domains
3. Issue Classification
Categorize all findings:
| Priority | Definition | Examples |
|---|---|---|
| Critical | Immediate security risk, fix now | Open database, no firewalls on prod |
| High | Significant risk, fix soon | SSH open to world, expired certs |
| Medium | Best practice violation | Missing backups, no monitoring |
| Low | Improvement opportunity | Inconsistent naming, missing tags |
4. Report Generation
Structure your report as:
# Infrastructure Security Audit Report
**Date**: YYYY-MM-DD
**Scope**: All DigitalOcean resources / Region: X / Tag: Y
## Executive Summary
- Resources audited: N
- Critical findings: N
- High findings: N
- Medium findings: N
- Low findings: N
## Critical Findings
### [Finding Title]
**Resource**: resource-name (resource-id)
**Issue**: Clear description of the problem
**Risk**: What could happen if not addressed
**Evidence**: Specific configuration showing the issue
**Remediation**:
1. Step-by-step fix instructions
2. Commands or tools to use
## High Findings
[Same format]
## Medium Findings
[Same format]
## Low Findings
[Same format]
## Recommendations
Prioritized list of improvements beyond immediate fixes.
## Verification Steps
How to confirm issues are resolved.
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.
- 9d ago First seen · 147 lines · 50 tokens per session scan A 7339a50ad11e
infrastructure-auditor is an agent published in the GitHub repository iamnolanhu/digitalocean-skills (4 stars, last pushed 7mo ago), licensed MIT. It adds 50 tokens to every session and 843 once invoked, about $0.0003 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…
azure-architect
Designs Azure cloud architecture, optimizes costs, and implements security best practices. Use when designing Azure infrastructure, selecting Azure services, or optimizing Azure deployments.
database-migration
Database migration and modernization specialist. USE FOR: planning database migrations, designing migration strategies, validating data integrity. DO NOT USE FOR: operational database management, routine backups.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
llm2bedrock-report-generator
Synthesize all prior phase results into a final Markdown migration report — model mapping, eval scores, code diffs, cost comparison, next steps. Writes MIGRATIONREPORT .md and returns a structured report object.
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.