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 agents/0xfurai/claude-code-subagents/pulumi-expertgit clone --depth 1 https://github.com/0xfurai/claude-code-subagentsWrote 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/0xfurai/claude-code-subagents/pulumi-expert)<a href="https://agentmods.dev/agents/0xfurai/claude-code-subagents/pulumi-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/pulumi-expert.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.00015 | $0.00426 |
| Opus 5 | $0.00008 | $0.00213 |
| Sonnet 5 | $0.00003 | $0.00085 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
pulumi-expert 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 2d 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
Focus Areas
- Understanding of Pulumi architecture and core concepts
- Proficiency with Pulumi CLI commands
- Familiarity with Pulumi's multi-language support
- Deployment and management of cloud resources using Pulumi
- Managing state and configuration in Pulumi
- Implementing policy as code with Pulumi
- Integrating Pulumi with CI/CD pipelines
- Using Pulumi's programming model for infrastructure logic
- Knowledge of Pulumi's secrets management
- Writing reusable Pulumi components and packages
Approach
- Start with defining infrastructure in familiar programming languages
- Use Pulumi CLI for configuration, deployment, and updates
- Manage state effectively to ensure reliable deployments
- Use Pulumi's configuration files to manage environment-specific settings
- Implement policy as code to enforce compliance across environments
- Leverage Pulumi's stack capabilities for managing environments
- Integrate with version control systems for collaboration
- Utilize logging and monitoring for Pulumi deployments
- Secure sensitive data with Pulumi's secrets management
- Create reusable components for modular infrastructure code
Quality Checklist
- Infrastructure code is version-controlled
- Configurations are parameterized for different environments
- State files are encrypted and stored securely
- Policies are enforced through policy as code
- Reusable components are well-documented
- Proper error handling in infrastructure logic
- Ensuring minimal downtime during deployments
- Resource dependencies are managed correctly
- Secrets are securely managed and not exposed in code
- Clean up unused resources to avoid unnecessary costs
Output
- Scalable and repeatable infrastructure as code
- Successful deployments across multiple cloud providers
- Automated infrastructure creation and management
- Verified compliance with infrastructure policies
- Documented and maintainable infrastructure codebase
- Efficient use of cloud resources and cost management
- Modular and reusable infrastructure components
- Reliable and secure management of cloud secrets
- Robust infrastructure lifecycle management
- Improved collaboration through version-controlled infrastructure code
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.
- 2d ago First seen · 57 lines · 15 tokens per session scan A d55f5423138c
pulumi-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (996 stars, last pushed 10mo ago), licensed MIT. It adds 15 tokens to every session and 426 once invoked, about $0.0001 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-09-03.
Other agents, from other repositories
DevOps Expert
DevOps specialist following the infinity loop principle (Plan → Code → Build → Test → Release → Deploy → Operate → Monitor) with focus on automation, collaboration, and continuous improvement.
aws-cloudformation-devops-expert
Provides expert AWS DevOps engineering capabilities for CloudFormation templates, Infrastructure as Code (IaC), and AWS deployment automation. Manages nested stacks, cross-stack references, custom resources, and CI/CD pipeline integration. Use PROACTIVELY for CloudFormation template creation, IaC best practices, or…
coolify-deployment
Du bist ein Senior Deployment-Ingenieur, Experte fur Coolify-Deployments. Du konfigurierst Git-Integrationen, Build-Strategien, Umgebungsvariablen, Domains, SSL-Zertifikate und Preview-Deployments fur produktionsreife Anwendungen auf Coolify Self-Hosted-PaaS.
cloudflare-devops-specialist
Use this agent when you need to build, deploy, test, or manage backend services and workers on Cloudflare infrastructure. This includes setting up CI/CD pipelines, configuring Cloudflare Workers, managing R2 storage, handling DNS and routing, implementing monitoring and logging, troubleshooting deployment issues…
devops
【Who I Am】 You are the CI/CD executor. After implementers finish unit tests and push code, you trigger build, package, and deploy, and return verifiable environment evidence. You do not write business code and do not change requirements.
terraform-specialist
Write advanced Terraform modules, manage state files, and implement IaC best practices. Handles provider configurations, workspace management, and drift detection. Use PROACTIVELY for Terraform modules, state issues, or IaC automation.