Borrowing it
Nothing to install: this file belongs to go-to-k/cdkd. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/go-to-k/cdkd/main/.claude/skills/run-integ/SKILL.mdgit clone --depth 1 https://github.com/go-to-k/cdkdWrote 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/go-to-k/cdkd/run-integ)<a href="https://agentmods.dev/skills/go-to-k/cdkd/run-integ"><img src="https://agentmods.dev/badge/skills/go-to-k/cdkd/run-integ.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.00034 | $0.05612 |
| Opus 5 | $0.00017 | $0.02806 |
| Sonnet 5 | $0.00007 | $0.01122 |
| Haiku 4.5 | $0.00003 | $0.00561 |
Grade A, and why
run-integ 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 today.
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.
curl -s -o /dev/null -w '%{http_code}\n' --max-time 15 https://registry-1.docker.io/v2/ # 401 = HOST networking fine How it starts
The opening of the file, as written. The whole thing — 384 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integration Test Runner
Run integration tests against a real AWS account: deploy actual resources, verify, clean up.
Arguments
test-name: which test (seels tests/integration/). If unspecified, ask viaAskUserQuestionshowing the options.all: run all tests--synth-only: synthesis only, skip deploy/destroy--no-destroy: deploy but don't destroy (debugging)--deploy-args "<args>": forward extra args to thecdkd deployinvocation verbatim (opt-in deploy flags; destroy is unaffected).
Steps
-
Build first:
vp run buildsodist/is current. -
List available tests:
ls tests/integration/— never a hardcoded list. -
Determine state bucket: account via
aws sts get-caller-identity --query Account --output text, thencdkd-state-{accountId}(region-free default since PR #62). If absent, fall back to legacycdkd-state-{accountId}-us-east-1and note the deprecation in the report. -
Pre-flight orphan scan (mandatory — fail fast on prior-run leftovers instead of going through CREATE + rollback): a prior run killed mid-deploy leaves orphans whose names match the stack about to deploy; cdkd's diff does not see them (not in state), so the deploy attempts CREATE and collides. Synth first (to learn stack name + resource types), then scan:
# Always (cheap, broadly applicable): aws s3 ls s3://<bucket>/cdkd/<StackName>/ --region us-east-1 aws iam list-roles --query 'Roles[?contains(RoleName, `<StackName>`)].RoleName' --output text aws lambda list-functions --region us-east-1 \ --query 'Functions[?contains(FunctionName, `<StackName>`)].FunctionName' --output text # When the template uses Lambda EventSourceMapping (orphan ESM = AlreadyExists + rollback): aws lambda list-event-source-mappings --region us-east-1 \ --query 'EventSourceMappings[?contains(FunctionArn, `<StackName>`)].[UUID,FunctionArn]' --output text # When the template uses VPC + Lambda VpcConfig (hyperplane ENIs outlive the function): aws ec2 describe-network-interfaces --region us-east-1 \ --filters "Name=description,Values=AWS Lambda VPC ENI-<StackName>*" \ --query 'NetworkInterfaces[].[NetworkInterfaceId,Status]' --output text
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.
- today Changed · +22 lines 5e5c461bf1c8
- yesterday Changed · +40 lines aa1f144617a6
- 3d ago Changed · -114 lines 285bc0314211
- 7d ago First seen · 436 lines · 34 tokens per session scan A a375d3c88261
run-integ is a skill published in the GitHub repository go-to-k/cdkd (135 stars, last pushed today), licensed Apache-2.0. It adds 34 tokens to every session and 5,612 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-08-30.
Other skills, from other repositories
aws-cdk-mcp-server-mcp
AWS Cloud Development Kit (CDK) best practices, infrastructure as code patterns, and security compliance with CDK Nag.
aws-testing
Testing strategies for AWS workloads. Use when writing unit tests, integration tests, contract tests, mocking AWS services, or setting up quality gates and CI/CD test pipelines.
python-runtime
Python toolchain configuration and best practices. Use when setting up Ruff, pytest, mypy type hints, dependency management, virtual environments or Python project standards.
playwright
Playwright E2E testing patterns. Trigger: When writing Playwright E2E tests (Page Object Model, selectors, MCP exploration workflow). For Prowler-specific UI conventions under ui/tests, also use prowler-test-ui.
prowler-test-sdk
Testing patterns for Prowler SDK (Python). Trigger: When writing tests for the Prowler SDK (checks/services/providers), including provider-specific mocking rules (moto for AWS only).
prowler-test-ui
E2E testing patterns for Prowler UI (Playwright). Trigger: When writing Playwright E2E tests under ui/tests in the Prowler UI (Prowler-specific base page/helpers, tags, flows).