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 mitodl/ol-infrastructure --skill new-pulumi-projectgit clone --depth 1 https://github.com/mitodl/ol-infrastructureWrote 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/mitodl/ol-infrastructure/new-pulumi-project)<a href="https://agentmods.dev/skills/mitodl/ol-infrastructure/new-pulumi-project"><img src="https://agentmods.dev/badge/skills/mitodl/ol-infrastructure/new-pulumi-project/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/mitodl/ol-infrastructure/new-pulumi-project"><img src="https://agentmods.dev/badge/skills/mitodl/ol-infrastructure/new-pulumi-project.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.00043 | $0.00911 |
| Opus 5 | $0.00022 | $0.00456 |
| Sonnet 5 | $0.00009 | $0.00182 |
| Haiku 4.5 | $0.00004 | $0.00091 |
Grade A, and why
new-pulumi-project 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 11d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating a New Pulumi Project
When to use
Use this skill whenever you need to create a new Pulumi project in the
ol-infrastructure monorepo — whether it's an infrastructure, application,
or substructure project.
Prerequisites
- You are at the root of the
ol-infrastructurerepo copier,pulumi, anduvare installed and on your PATH- You are logged in to Pulumi:
pulumi login s3://mitol-pulumi-state
Steps
1. Create a feature branch
git checkout -b <branch-name>
2. Scaffold the project with copier
Run from the repo root. Copier will interactively prompt for:
- project_name — snake_case name used for the directory and stack prefix (e.g.
qdrant_cloud) - project_type — one of
application,substructure, orinfrastructure - project_description — human-readable description for
Pulumi.yaml
You should choose a target module path under src/ol_infrastructure that matches the
existing directory layout for the kind of project you're creating. For example:
- Application:
applications/<project_name> - Infrastructure:
infrastructure/aws/<project_name>(or another direct child path that matches existing projects) - Substructure:
substructure/<project_name>(or a more specific nested path under an existing substructure hierarchy, if applicable)
Use that module path as the copier destination:
copier copy copier_templates/pulumi_project/ src/ol_infrastructure/<target_module_path>
The generated Pulumi.yaml backend is pre-set to s3://mitol-pulumi-state/.
3. Initialize stacks
Navigate into the new project directory and initialize CI, QA, and Production stacks. Each stack uses a KMS key scoped to its environment.
cd src/ol_infrastructure/<target_module_path>
# <namespace> should match the dotted module path for this project,
# for example: applications.mitxonline or infrastructure.aws.myproject
pulumi stack init <namespace>.CI \
--secrets-provider=awskms://alias/infrastructure-secrets-ci
pulumi stack init <namespace>.QA \
--secrets-provider=awskms://alias/infrastructure-secrets-qa
pulumi stack init <namespace>.Production \
--secrets-provider=awskms://alias/infrastructure-secrets-production
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.
- 11d ago First seen · 106 lines · 43 tokens per session scan A 268c25273240
new-pulumi-project is a skill published in the GitHub repository mitodl/ol-infrastructure (58 stars, last pushed today), licensed BSD-3-Clause. It adds 43 tokens to every session and 911 once invoked, about $0.0002 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
aws-collector-tool
AWS infrastructure collector. Fetches ECS status, CloudWatch logs, and metrics. Use when: checking ECS health, inspecting CloudWatch error logs, pulling infra metrics, or monitoring AWS resources.
kubectl_onprem
On-prem Kubernetes cluster integration for running kubectl commands via Aurora agent relay or uploaded kubeconfig.
aws-essentials
Use when standing up the core AWS surface a small product needs: hardening a fresh account, a private S3 bucket, encrypted RDS Postgres, ECS Fargate vs EC2, CloudFront + OAC, or scoping an IAM policy to least privilege. NOT the CI pipeline that ships the container (that is deployment), NOT app-code access-control…
aws-expert
Expert-level AWS cloud architecture, services, security, cost optimization, and best practices. Use when the user mentions cloud, infrastructure, devops, or serverless, or when the task involves Compute Services, Storage Services, Database Services, or Networking.
aws-cloud-penetration-testing
Penetration test AWS cloud environments for misconfigurations, privilege escalation, data exposure, and lateral movement. Use this skill when assessing AWS accounts for security weaknesses including S3 bucket misconfigurations, IAM policy flaws, EC2 metadata exploitation, Lambda function abuse, and cross-account…
aws-cdk-discipline
AWS infrastructure policy for fermi-agentcore - all changes through CDK committed to main, Fermi AWS access is read-only verification.