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 jpd44/mesh44-plugins --skill cdk-stackgit clone --depth 1 https://github.com/jpd44/mesh44-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/jpd44/mesh44-plugins/cdk-stack)<a href="https://agentmods.dev/skills/jpd44/mesh44-plugins/cdk-stack"><img src="https://agentmods.dev/badge/skills/jpd44/mesh44-plugins/cdk-stack/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/jpd44/mesh44-plugins/cdk-stack"><img src="https://agentmods.dev/badge/skills/jpd44/mesh44-plugins/cdk-stack.svg" alt="Reviewed on agentmods" width="80" 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.00044 | $0.02046 |
| Opus 5.5 | $0.00018 | $0.00818 |
| Sonnet 5.5 | $0.00009 | $0.00409 |
| Haiku 4.5 | $0.00004 | $0.00205 |
Grade A, and why
cdk-stack 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/app-kit:cdk-stack — render and deploy infra
This mirrors daily-deutsch/cdk/: S3 (private, OAC) → CloudFront (apex + www, ACM, www-to-apex redirect, SPA error rewrite) → Route 53 alias records → CodeStar GitHub connection → CodeBuild test + CodeBuild build/deploy → CodePipeline V2 with Source/Test/BuildAndDeploy stages.
Inputs
From the orchestrator: app_name, aws_account_id, github_owner (defaults to github.org from config), github_branch (defaults main), domain (string OR null), and three independent toggles:
needs_cognito(bool) — adds Cognito UserPool + UserPoolClientneeds_api(bool) — adds HTTP API Gateway + JWT authorizer + sample protected Lambda. Requiresneeds_cognito=true; refuse otherwise.needs_llm_lambda(bool) — adds the daily-deutsch-style unauth'd Bedrock Lambda Function URL
If domain is null the app is served from the CloudFront default URL only (no Route 53, no ACM cert, no www→apex redirect).
Steps
1. Copy the template
Pick templates/vite/cdk/ or templates/nextjs/cdk/ based on the user's stack choice. Copy into <app-path>/cdk/. Rename lib/stack.ts to lib/<app-name>-stack.ts (the import in bin/app.ts expects this). Then walk the tree and replace placeholders:
| Placeholder | Replacement |
|---|---|
{{APP_NAME}} |
kebab-case (daily-deutsch) |
{{APP_NAME_PASCAL}} |
PascalCase (DailyDeutsch) |
{{DOMAIN}} |
apex (daily-deutsch.com) |
{{AWS_ACCOUNT_ID}} |
child account ID |
{{GITHUB_OWNER}} |
github.org from config unless overridden |
{{GITHUB_BRANCH}} |
usually main |
Strip the blocks the user didn't pick. The template has these block-pair markers in lib/<app-name>-stack.ts and bin/app.ts. Block-pair stripping = delete everything from the // BEGIN_X line through the matching // END_X line, inclusive.
| Condition | Markers to keep | Markers to strip |
|---|---|---|
domain is a string |
BEGIN_DOMAIN / END_DOMAIN |
BEGIN_NO_DOMAIN / END_NO_DOMAIN |
domain is null |
BEGIN_NO_DOMAIN / END_NO_DOMAIN |
BEGIN_DOMAIN / END_DOMAIN |
needs_llm_lambda=false |
— | BEGIN_LLM_LAMBDA / END_LLM_LAMBDA (all occurrences). Also delete lambda/llm/ directory. |
needs_cognito=false |
— | BEGIN_COGNITO / END_COGNITO (all occurrences). |
needs_api=false |
— | BEGIN_API / END_API (all occurrences). Also delete lambda/hello-protected/ directory. |
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 First seen · 131 lines · 44 tokens per session scan A 98344e579582
cdk-stack is a skill published in the GitHub repository jpd44/mesh44-plugins (2 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 2,046 once invoked, about $0.0002 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-31.
Other skills, from other repositories
mirrord-prev-env
Help users create and manage mirrord preview environments — running a modified service as an isolated pod in a shared Kubernetes cluster, scoped by an environment key and HTTP/queue traffic filtering, so teams can validate and review changes against real traffic without affecting live services. Use when a developer…
mirrord-chaos
Help users chaos test their app with mirrord: inject artificial latency or connection errors into a mirrord session's outgoing traffic via per-session chaos rules managed with the mirrord chaos CLI. Use when a user wants to add latency or delay to outgoing connections or a dependency (e.g. a slow database), simulate…
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.
atmos-modernization
Atmos Modernization: migrate deprecated or legacy Atmos patterns to current names, Native CI, Atmos Pro drift detection, dependencies.components, nametemplate, and declared secrets.
atmos-sbom
Atmos SBOM provenance: CycloneDX and SPDX generation from vendor and Terraform evidence, coverage diagnostics, NTIA validation, and native CI workflow-artifact publication.
atmos-pro
Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection.