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/mitodl/agent-kit/pulumi-modify-existingnpx skills add mitodl/agent-kit --skill pulumi-modify-existinggit clone --depth 1 https://github.com/mitodl/agent-kitWrote 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/agent-kit/pulumi-modify-existing)<a href="https://agentmods.dev/skills/mitodl/agent-kit/pulumi-modify-existing"><img src="https://agentmods.dev/badge/skills/mitodl/agent-kit/pulumi-modify-existing.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.1 | $0.00056 | $0.00317 |
| Opus 5 | $0.00028 | $0.00159 |
| Sonnet 5 | $0.00011 | $0.00063 |
| Haiku 4.5 | $0.00006 | $0.00032 |
Grade A, and why
pulumi-modify-existing 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.
What it actually says
Pulumi: Modify Existing Files
Always modify, never create
Infrastructure changes belong in the existing entrypoint for the stack
(typically __main__.py). Do not create additional Pulumi files unless the stack
already follows a multi-file pattern that makes a new file the right fit.
Preserve existing functionality
When editing a Pulumi stack entrypoint, the following must never be silently removed:
assumeRole/ cross-account role configuration — removing this breaks production deployments that depend on cross-account access.- Existing resource exports (
pulumi.export(...)). - Stack references to other stacks.
Before finalizing changes, scan the diff to confirm nothing was deleted unintentionally.
Validate changes before declaring done
After modifying any Pulumi code, run a preview to confirm the plan is correct:
pulumi preview --stack <stack-name>
Review the output carefully:
- Unexpected resource replacements or deletions are bugs, not acceptable side effects.
- "0 changes" is only correct if you genuinely expected no changes.
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 First seen · 46 lines · 56 tokens per session scan A 0d68fd3213ab
pulumi-modify-existing is a skill published in the GitHub repository mitodl/agent-kit (2 stars, last pushed yesterday), licensed BSD-3-Clause. It adds 56 tokens to every session and 317 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 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…