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/go-to-k/cdkd/check-docsnpx skills add go-to-k/cdkd --skill check-docsgit 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/check-docs)<a href="https://agentmods.dev/skills/go-to-k/cdkd/check-docs"><img src="https://agentmods.dev/badge/skills/go-to-k/cdkd/check-docs.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.00039 | $0.01640 |
| Opus 5 | $0.00019 | $0.00820 |
| Sonnet 5 | $0.00008 | $0.00328 |
| Haiku 4.5 | $0.00004 | $0.00164 |
Grade A, and why
check-docs 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 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.
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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Consistency Check
You are checking whether documentation is up to date with recent code changes in this repository.
Steps
-
Identify what changed: Run
git diff main...HEAD --name-only(orgit diff HEAD~5 --name-onlyif on main) to see recently changed source files. -
Decide whether a deep review is needed (short-circuit). The
docsgate's scope includessrc/**, so any src edit invalidates the marker — but most internal refactors and bug fixes don't affect anything the docs describe. Skip the LLM-judged review and set the marker directly when the diff only touches files that the docs don't describe. A deep review is required if the diff touches ANY of:src/index.ts— public exportssrc/cli/options.ts,src/cli/commands/**— CLI surface described in docs/getting-started.md and the per-command pages under docs/ (the README's usage sections moved there)src/types/**— public type definitionssrc/state/**— bucket name, key layout, lock layout, schema version. These are documented verbatim indocs/state-management.md,docs/troubleshooting.md,docs/stack-outputs.md(the "Outputs" example path), and CLAUDE.md ("S3 storage structure"). A path-layout change ins3-state-backend.tsorlock-manager.tsinvalidates ~30 shell snippets across those files; the auto-migration session of 2026-05-01 (PR #57 → v0.7.0) shipped before this trigger existed and the docs took the full rollout to be re-aligned.- any new file added anywhere under
src/**— must be mentioned in CLAUDE.md "Key Files and Directories" package.json— dependency additions/removals described in CLAUDE.md "Dependencies"README.md,CLAUDE.md,docs/**,.claude/rules/**— the docs themselves- README-visible CLI behavior changes (new flags, changed defaults, new commands)
If none of the above apply (only internal src files modified, no new files, no deps changed), write a one-line note — "no docs-visible surface touched" — set the
docsmarker (see "Commit-gate marker" below), and stop. Do NOT re-read docs for unrelated internal edits.
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 f2a878ce9947
- yesterday Changed 7f0ea8693e3b
- 5d ago First seen · 71 lines · 39 tokens per session scan A 0114626b9757
check-docs is a skill published in the GitHub repository go-to-k/cdkd (132 stars, last pushed today), licensed Apache-2.0. It adds 39 tokens to every session and 1,640 once invoked, about $0.0002 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
aws-cdk-mcp-server-mcp
AWS Cloud Development Kit (CDK) best practices, infrastructure as code patterns, and security compliance with CDK Nag.
agent-squad-python
Use when building or modifying a Python app that uses the agent-squad Python package — async multi-agent orchestration for Python 3.11+: orchestrator, agents (BedrockLLMAgent, AnthropicAgent, OpenAIAgent, SupervisorAgent, GroundedAgent, ChainAgent, and more), classifier routing (Bedrock, Anthropic, OpenAI), storage…
agent-squad-typescript
Use when building or modifying a Node.js / TypeScript app that uses the agent-squad npm package — multi-agent orchestration: orchestrator, agents (all built-in types + GroundedAgent), classifier routing (Bedrock / Anthropic / OpenAI), storage (in-memory / DynamoDB / SQL), retrievers (Amazon KB / Dakera), and tools…
agent-squad-swift
Use when building or modifying a Swift app that uses the AgentSquad Swift framework — on-device multi-agent orchestration for iOS 16+ / macOS 14+: orchestrator, agents (Agent, GroundedAgent), classifier routing, LLM clients (OpenAI-compatible), tools (native + MCP), tool UIs/widgets, on-device storage, tracing, and…
nx-plugin-for-aws
Scaffold and build cloud-native applications on AWS using @aws/nx-plugin generators. Use when the user wants to create workspaces, generate projects, or scaffold infrastructure with the Nx Plugin for AWS.
aws-cdk-development
AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python. Use when creating CDK stacks, defining CDK constructs, implementing infrastructure as code, or when the user mentions CDK, CloudFormation, IaC, cdk synth, cdk deploy, or wants to define AWS infrastructure programmatically.…