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/nevaberry/nevaberry-plugins/aws-cdk-knowledge-patchnpx skills add Nevaberry/nevaberry-plugins --skill aws-cdk-knowledge-patchgit clone --depth 1 https://github.com/Nevaberry/nevaberry-pluginsWrote 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/nevaberry/nevaberry-plugins/aws-cdk-knowledge-patch)<a href="https://agentmods.dev/skills/nevaberry/nevaberry-plugins/aws-cdk-knowledge-patch"><img src="https://agentmods.dev/badge/skills/nevaberry/nevaberry-plugins/aws-cdk-knowledge-patch.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 | $0.00011 | $0.02367 |
| Opus 5 | $0.00005 | $0.01184 |
| Sonnet 5 | $0.00002 | $0.00473 |
| Haiku 4.5 | $0.00001 | $0.00237 |
Grade A, and why
aws-cdk-knowledge-patch 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 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.
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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS CDK Knowledge Patch
Load this skill when changing, reviewing, debugging, or upgrading AWS CDK applications, construct libraries, CLI integrations, or synthesized CloudFormation templates.
Prefer the project's manifests, lockfiles, source, synthesized output, and tests when they disagree with this guidance. Apply feature-flagged behavior only when the relevant flag is enabled.
Reference index
| Reference | Topics |
|---|---|
| Compute delivery and workflows | Lambda, custom resources, Step Functions, CodeBuild, CodePipeline, assets, Auto Scaling, Batch, and EC2 |
| Containers and Kubernetes | ECS, EKS, ECR, MSK, deployment strategies, add-ons, and platform versions |
| Core toolkit and validation | CLI, bootstrap, import, synthesis, context, feature flags, validation, errors, and Mixins |
| Events, messaging, and streaming | EventBridge, Scheduler, Kinesis, Data Firehose, SNS, SQS, and Kafka event sources |
| Generated contracts and types | L1 schema changes, generated imports and guards, reference interfaces, and grants |
| Identity, security, and AI | Cognito, IAM, KMS, Secrets Manager, certificates, Bedrock, and AgentCore |
| Networking, APIs, and edge | API Gateway, AppSync, CloudFront, Elastic Load Balancing, Route 53, VPC, and Cloud WAN |
| Observability and service integrations | CloudWatch, Logs, Synthetics, AppConfig, SES, EMR, Glue, and media services |
| Storage and databases | S3, S3 Tables, RDS, Aurora, DynamoDB, OpenSearch, DocumentDB, EFS, and ElastiCache |
First-pass compatibility audit
Before editing an established application:
What ships with it
10 files 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.
- coverage.json 2.2 KB
- references/compute-delivery-and-workflows.md 11 KB
- references/containers-and-kubernetes.md 6.1 KB
- references/core-toolkit-and-validation.md 6.1 KB
- references/events-messaging-and-streaming.md 3.7 KB
- references/generated-contracts-and-types.md 8.7 KB
- references/identity-security-and-ai.md 4.2 KB
- references/networking-apis-and-edge.md 5.8 KB
- references/observability-and-service-integrations.md 5.3 KB
- references/storage-and-databases.md 8.3 KB
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 · 183 lines · 11 tokens per session scan A 1f70ea192c4d
aws-cdk-knowledge-patch is a skill published in the GitHub repository Nevaberry/nevaberry-plugins (24 stars, last pushed 7d ago), licensed MIT. It adds 11 tokens to every session and 2,367 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-08-30.
Other skills, from other repositories
api-workers
Cloudflare Workers deployment using createWorkerHandler from @cyanheads/mcp-ts-core/worker. Covers the full handler signature, binding types, CloudflareBindings extensibility, runtime compatibility guards, and wrangler.toml requirements.
healthcheck
Host security hardening and risk-tolerance configuration for OpenClaw deployments. Use when a user asks for security audits, firewall/SSH/update hardening, risk posture, exposure review, OpenClaw cron scheduling for periodic checks, or version status checks on a machine running OpenClaw (laptop, workstation, Pi, VPS).
api-context
Canonical reference for the unified Context object passed to every tool and resource handler in @cyanheads/mcp-ts-core. Covers the full interface, its RequestContext base, all sub-APIs (ctx.log, ctx.state, ctx.requestInput, ctx.inputs, ctx.enrich, ctx.content), and when to use each.
api-testing
Testing patterns for MCP tool/resource handlers using createMockContext and Vitest. Covers mock context options, handler testing, McpError assertions, format testing, Vitest config setup, and test isolation conventions.
api-telemetry
Catalog of OpenTelemetry instrumentation built into framework @cyanheads/mcp-ts-core — spans, metrics, completion logs, env config, runtime caveats, custom instrumentation patterns, and cardinality rules. Use when enabling OTel export, adding custom spans or metrics in services, debugging missing telemetry, looking up…
maintenance
Investigate, adopt, and verify dependency updates — with special handling for @cyanheads/mcp-ts-core. Captures what changed, understands why, cross-references against the codebase, adopts framework improvements, syncs project skills, and runs final checks. Supports two entry modes: run the full flow end-to-end, or…