Borrowing it
Nothing to install: this file belongs to pavel-molyanov/molyanov-ai-dev. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/pavel-molyanov/molyanov-ai-dev/main/.agents/skills/infrastructure-setup/SKILL.mdgit clone --depth 1 https://github.com/pavel-molyanov/molyanov-ai-devWrote 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/pavel-molyanov/molyanov-ai-dev/infrastructure-setup)<a href="https://agentmods.dev/skills/pavel-molyanov/molyanov-ai-dev/infrastructure-setup"><img src="https://agentmods.dev/badge/skills/pavel-molyanov/molyanov-ai-dev/infrastructure-setup/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/pavel-molyanov/molyanov-ai-dev/infrastructure-setup"><img src="https://agentmods.dev/badge/skills/pavel-molyanov/molyanov-ai-dev/infrastructure-setup.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.00080 | $0.01183 |
| Opus 5.5 | $0.00032 | $0.00473 |
| Sonnet 5.5 | $0.00016 | $0.00237 |
| Haiku 4.5 | $0.00008 | $0.00118 |
Grade A, and why
infrastructure-setup 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Infrastructure Conventions
Scope and Judgment
- Project Knowledge is required infrastructure context. If it is absent, stop and ask the user to create or fill it before continuing.
- The user's request defines which changes are authorized. A request to inspect, review, or assess current infrastructure authorizes diagnosis and recommendations, not implementation.
- Existing architecture and Project Knowledge are the current contract, not proof that the setup is good. Report demonstrated defects, unnecessary complexity, unsafe behavior, operational risks, and worthwhile improvements instead of silently accepting them.
- Do not implement an improvement outside the user's request merely because it is beneficial. Explain the evidence, impact, and proposed direction, then obtain agreement before changing it.
- Discuss the situation with the user when material information is missing or contradictory, an action can affect production, users, data, secrets, or neighboring projects, the safe result is uncertain, the current setup appears wrong, or the intended response expands the request.
- Treat a rare or unagreed operational scenario as a user decision even when its correction looks local. Ask before adding or changing delivery, recovery, monitoring, isolation, persistent state, infrastructure entities, dependencies, architecture, or material complexity.
- Apply only the topic rules relevant to the request; these are conventions, not a required setup sequence.
Project-Specific Ownership
- Concrete hosts, platforms, users, paths, ports, service names, deployment triggers, direct-access policy, agent or operations host, monitoring location, notification route, backup destinations, and emergency recovery facts belong in Project Knowledge's deployment owner.
- Keep those facts current through
documentation-writingwhen an infrastructure change alters them. Do not copy private project facts into this global skill or another public methodology file. - Project-specific decisions override the generic patterns here. If a documented choice is risky or no longer fits reality, report it and discuss a change rather than overriding it silently.
What ships with it
3 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.
- 6d ago Changed · -27 lines · -33 tokens per session 2c6a1c77b704
- 1mo ago First seen · 122 lines · 113 tokens per session scan A 6b416c20c093
infrastructure-setup is a skill published in the GitHub repository pavel-molyanov/molyanov-ai-dev (300 stars, last pushed 6d ago), licensed MIT. It adds 80 tokens to every session and 1,183 once invoked, about $0.0003 per session on Opus 5.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
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
gear
Managing dependencies, CI/CD, advanced GitHub Actions workflows, containers, secrets, and operational config. Use for build, workflow, or environment work.
devops
You are the DevOps Specialist -- the single authority on version control, CI/CD pipelines, platform operations (GitHub, Azure DevOps, GitLab), infrastructure, deployment, backup, and cleanup. If it touches git, pipelines, or production infrastructure, it's yours.
cuelabs-delivery-standard
Audit, create, or standardize CueLABS delivery systems. Use for GitHub Actions, CI parity, release workflows, Dockerfiles, Docker Compose, Helm, Terraform, Cloud Run, Firebase App Hosting, environment variables, OpenTelemetry, artifacts, or deployment readiness.
devops-zeroclaw-coordination-rules
ZEROCLAW COORDINATION RULES — extracted from roles.json deepPrompt for devops.
dockerized-service-release-deployment-workflow
Create a Dockerized-service release contract with clean GitHub Actions builds, main-anchored tags, immutable digest manifests, published-release deployments, production approval, health checks, and exact-digest rollback.