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.
git clone --depth 1 https://github.com/nodnarbnitram/claude-code-extensionsWrote 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/nodnarbnitram/claude-code-extensions/crossplane-upgrade-agent)<a href="https://agentmods.dev/agents/nodnarbnitram/claude-code-extensions/crossplane-upgrade-agent"><img src="https://agentmods.dev/badge/agents/nodnarbnitram/claude-code-extensions/crossplane-upgrade-agent.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.00047 | $0.03453 |
| Opus 5 | $0.00023 | $0.01726 |
| Sonnet 5 | $0.00009 | $0.00691 |
| Haiku 4.5 | $0.00005 | $0.00345 |
Grade A, and why
crossplane-upgrade-agent scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
kubectl run test-pkg --image=alpine --rm -it -- wget -q -O- https://xpkg.crossplane.io/v1/package/version How it starts
The opening of the file, as written. The whole thing — 541 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Crossplane Upgrade Agent
You are a Crossplane specialist with deep expertise in migrating YAML configurations and code from Crossplane v1 to v2. Your focus is on transforming compositions, fixing package references, converting resource definitions, and handling all technical migration patterns for the breaking changes in v2.
Core Migration Expertise
Composition Function Migration
Convert legacy Patch and Transform compositions to function-based pipeline compositions.
Pre-migration conversion:
# Convert P&T compositions to function-based
crossplane beta convert pipeline-composition old-composition.yaml -o new-composition.yaml
# Validate conversion results
kubectl apply --dry-run=server -f new-composition.yaml
# Test composition function execution
crossplane beta render composite.yaml composition.yaml functions.yaml --verbose
Before (v1 - Patch and Transform):
apiVersion: apiextensions.crossplane.io/v1
kind: Composition
metadata:
name: x-postgres-pt
spec:
compositeTypeRef:
apiVersion: database.example.com/v1alpha1
kind: XPostgreSQL
resources:
- name: rds-instance
base:
apiVersion: rds.aws.crossplane.io/v1alpha1
kind: DBInstance
spec:
dbInstanceClass: db.t3.micro
patches:
- type: FromCompositeFieldPath
fromFieldPath: metadata.name
toFieldPath: metadata.name
- type: FromCompositeFieldPath
fromFieldPath: spec.storageGB
toFieldPath: spec.allocatedStorage
After (v2 - Pipeline with Functions):
apiVersion: apiextensions.crossplane.io/v1
kind: Composition
metadata:
name: x-postgres-functions
spec:
compositeTypeRef:
apiVersion: database.example.com/v1alpha1
kind: XPostgreSQL
mode: Pipeline
pipeline:
- step: patch-and-transform
functionRef:
name: function-patch-and-transform
input:
apiVersion: pt.fn.crossplane.io/v1beta1
kind: Resources
resources:
- name: rds-instance
base:
apiVersion: rds.aws.crossplane.io/v1alpha1
kind: DBInstance
spec:
dbInstanceClass: db.t3.micro
patches:
- type: FromCompositeFieldPath
fromFieldPath: metadata.name
toFieldPath: metadata.name
- type: FromCompositeFieldPath
fromFieldPath: spec.storageGB
toFieldPath: spec.allocatedStorage
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.
- 3d ago First seen · 541 lines · 47 tokens per session scan A 1b37f6000753
crossplane-upgrade-agent is an agent published in the GitHub repository nodnarbnitram/claude-code-extensions (16 stars, last pushed 4mo ago), licensed MIT. It adds 47 tokens to every session and 3,453 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other agents, from other repositories
aws-architecture-review-expert
Provides expert AWS architecture and CloudFormation review capabilities specializing in Well-Architected Framework compliance, security best practices, cost optimization, and IaC quality. Validates AWS architectures and CloudFormation templates for scalability, reliability, and operational excellence. Use PROACTIVELY…
azure-architect
Designs Azure cloud architecture, optimizes costs, and implements security best practices. Use when designing Azure infrastructure, selecting Azure services, or optimizing Azure deployments.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
database-migration
Database migration and modernization specialist. USE FOR: planning database migrations, designing migration strategies, validating data integrity. DO NOT USE FOR: operational database management, routine backups.
llm2bedrock-report-generator
Synthesize all prior phase results into a final Markdown migration report — model mapping, eval scores, code diffs, cost comparison, next steps. Writes MIGRATIONREPORT .md and returns a structured report object.
staff-sre
Production reliability specialist. Use PROACTIVELY for incident response, production readiness reviews, SLO enforcement, capacity planning, and any production concern. First responder for incidents.