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 pulumi/agent-skills --skill pulumi-context-apigit clone --depth 1 https://github.com/pulumi/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/pulumi/agent-skills/pulumi-context-api)<a href="https://agentmods.dev/skills/pulumi/agent-skills/pulumi-context-api"><img src="https://agentmods.dev/badge/skills/pulumi/agent-skills/pulumi-context-api/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/pulumi/agent-skills/pulumi-context-api"><img src="https://agentmods.dev/badge/skills/pulumi/agent-skills/pulumi-context-api.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.00153 | $0.01370 |
| Opus 5.5 | $0.00061 | $0.00548 |
| Sonnet 5.5 | $0.00031 | $0.00274 |
| Haiku 4.5 | $0.00015 | $0.00137 |
Grade A, and why
pulumi-context-api 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 1mo 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Query the Pulumi Context API
The Context API answers questions about an organization's cloud infrastructure as a graph: what exists, what depends on what, what a change would affect. It covers resources found through Pulumi Discovery, not just Pulumi-managed ones.
Prefer it over Resource Search whenever the question involves relationships. Resource Search finds individual resources but cannot follow edges, so answering "what depends on X" with repeated searches is slow and usually incomplete.
Public preview, for organizations on the Enterprise and Business Critical
editions, and a role granting resources:search (the default Member and Admin
roles do).
First: is a graph tool already in the session?
If one is — graph_query and get_graph_schema, under whatever prefix the
server registers them — call it and skip Steps 1 and 2. Compose the selector
from the graph_query tool's own description, which carries the grammar; the
tool resolves the organization and credentials itself and drains pagination for
you. When that description is not enough, get_graph_schema returns the live
field vocabulary and limits, and will serve the full Step 1 primer when asked
for it. Step 3 still governs what you do with the result.
Steps 1 and 2 are the path for an agent that has a shell and no such tool.
Step 1: fetch the primer, always
Needs Pulumi CLI v3.243.0 or newer and an active pulumi login.
pulumi api GetGraphQuerySchema --output=markdown
This returns a self-contained guide to composing selectors — vocabulary, edge types, engine caps, worked examples, pagination, completeness rules, the gates that deny a query, and the traps that produce a confident wrong answer instead of an error. It is served by the deployment that answers your queries, so it is the contract, and it moves between schema versions. This skill bootstraps you to it and stops there; everything below defers to it. Fetch it fresh in every session — a primer remembered from earlier may describe a schema this deployment no longer serves.
What ships with it
1 file 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.
- 1mo ago Changed · +14 lines 0a8df7bfeee6
- 1mo ago Changed · +6 lines 32c34e055acf
- 1mo ago First seen · 110 lines · 153 tokens per session scan A 77f1b12fadf5
pulumi-context-api is a skill published in the GitHub repository pulumi/agent-skills (78 stars, last pushed 16d ago), licensed Apache-2.0. It adds 153 tokens to every session and 1,370 once invoked, about $0.0006 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
infrastructure-as-code-guardian
Universal Infrastructure as Code (IaC) agent skill for authoring, securing, and managing cloud infrastructure across Terraform, Pulumi, CloudFormation, Ansible, and Bicep. Provides cross-tool security hardening, state management best practices, cost optimization, drift detection, and CI/CD integration. Covers AWS…
terraform-expert
Expert-level Terraform infrastructure as code, modules, state management, and production best practices. Use when the user mentions infrastructure as code, devops, or automation, or when the task involves Terraform Basics, Resource Management, Modules, or State Management.
terraform-docs
Terraform 1.15.x — configuration language, resources, variables, modules, state, backends, providers, functions.
Terraform Infrastructure as Code
Production-grade Terraform development with HCL best practices, module design, state management, multi-cloud patterns, and AI-enhanced infrastructure as code for scalable cloud deployments.
activate-site
Activates and provisions a Power Pages website in a Power Platform environment via the Power Platform REST API. Use when the user wants to activate, provision, turn on, or enable a Power Pages website or portal.
auditing-terraform-infrastructure-for-security
Auditing Terraform infrastructure-as-code for security misconfigurations using Checkov, tfsec, Terrascan, and OPA/Rego policies to detect overly permissive IAM policies, public resource exposure, missing encryption, and insecure defaults before cloud deployment.