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 agentmods add skills/avizmarlon/agent-skills/iac-first-commitnpx skills add avizmarlon/agent-skills --skill iac-first-commitgit clone --depth 1 https://github.com/avizmarlon/agent-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/avizmarlon/agent-skills/iac-first-commit)<a href="https://agentmods.dev/skills/avizmarlon/agent-skills/iac-first-commit"><img src="https://agentmods.dev/badge/skills/avizmarlon/agent-skills/iac-first-commit.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 | $0.00078 | $0.02174 |
| Opus 5 | $0.00039 | $0.01087 |
| Sonnet 5 | $0.00016 | $0.00435 |
| Haiku 4.5 | $0.00008 | $0.00217 |
Grade A, and why
iac-first-commit 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 5d 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Infrastructure-as-Code (IaC) from First Commit
Core principle: Every new project, from its first commit, must be fully rebuildable from zero using only git clone + a single, documented bootstrap command. All infrastructure state is declarative, version-controlled, and reproducible without tribal knowledge or manual steps.
Why this matters
- Reproducibility: A new team member (or the original author months later) can spin up the entire environment deterministically.
- Reliability: Infrastructure changes are reviewed in pull requests, tested in CI, and rollback-safe.
- Disaster recovery: Loss of a server or credential requires only re-running the bootstrap process.
- Onboarding: No "run these commands manually" instructions; no "remember to configure this first."
Mental test before scaffolding any project
"If another person or an AI agent needed to rebuild this project from zero right now, would git clone <repo> && ./bootstrap.sh be sufficient? Or are there undocumented, manual steps?"
If the answer is "there are manual steps," the project lacks proper IaC coverage.
Tool selection by context
Use the IaC tool native to your infrastructure platform. There is no one-size-fits-all tool — the platform dictates the choice:
| Context | Native IaC Tool | Example |
|---|---|---|
| VPS / Linux server | Ansible (configuration) + Terraform (if cloud provisioning) | ansible-playbook site.yml |
| Frontend SaaS (Next.js, Vite, etc.) | Platform config-as-code + GitHub Actions | Vercel/Netlify/Cloudflare Pages deployment config |
| Serverless APIs (AWS Lambda, Cloudflare Workers) | SST / SAM / CDK / Wrangler | sst deploy or wrangler deploy |
| Mobile (iOS, Android, Expo) | Fastlane + EAS/Code Push config | fastlane build + eas build |
| Kubernetes | ArgoCD / Flux + Helm charts | GitOps with declarative manifests in git |
| ML / data pipelines | DVC + MLflow + Airflow DAGs | Reproducible training/inference pipelines |
| Browser extension / desktop app | Build manifest + bundler config + CI/CD | GitHub Actions release workflow |
| Static docs / sites | GitHub Actions + hosting provider config | Build → upload → serve, automated |
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.
- 5d ago First seen · 182 lines · 78 tokens per session scan A fa9cfd7fbf09
iac-first-commit is a skill published in the GitHub repository avizmarlon/agent-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 78 tokens to every session and 2,174 once invoked, about $0.0004 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 skills, from other repositories
subagent-driven-development
Execute plans via delegatetask subagents (2-stage review).
duckduckgo-search
Free keyless web, news, and image search via ddgs.
mcporter
List, auth, and call MCP servers/tools from the terminal.
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
complete-partial-pr
Evaluate and complete an issue or PR where the submitted patch fixes only a narrow symptom of the reported pain point. Use when a contribution may miss adjacent integration surfaces, provider/spec semantics, roundtrip behavior, tests, docs, or historical maintainer decisions.