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/knocklabs/skills/knock-clinpx skills add knocklabs/skills --skill knock-cligit clone --depth 1 https://github.com/knocklabs/skillsWrote 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/knocklabs/skills/knock-cli)<a href="https://agentmods.dev/skills/knocklabs/skills/knock-cli"><img src="https://agentmods.dev/badge/skills/knocklabs/skills/knock-cli.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.00027 | $0.01908 |
| Opus 5 | $0.00014 | $0.00954 |
| Sonnet 5 | $0.00005 | $0.00382 |
| Haiku 4.5 | $0.00003 | $0.00191 |
Grade A, and why
knock-cli 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Knock CLI skill
This skill provides comprehensive guidelines for working with the Knock CLI to manage workflows, templates, and other notification resources.
Overview
The Knock CLI skill includes detailed rule sets covering:
- CLI installation and authentication - How to install and authenticate with the Knock CLI
- Knock directory structure - Understanding the knock directory layout and configuration
- CLI commands reference - Pull, push, and resource management commands
- Workflow templates - Structures, patterns, and best practices for workflows and templates
- Guides and message types - Working with in-app guides for lifecycle messaging and message types as their schema
- Partials - Reusable template building blocks for email design systems
How to use this skill
For initial setup
When setting up a new project with Knock:
-
Start with installation and authentication (
rules/cli-installation-authentication.md)- Verify the CLI is installed
- Authenticate with a service token or dashboard account
- Initialize the project with
knock init
-
Understand the directory structure (
rules/knock-directory-structure.md)- Learn the knock.json configuration
- Understand resource organization
For managing resources
When working with Knock resources:
-
Use the CLI commands reference (
rules/cli-commands-reference.md)- Pull resources from Knock to your local project
- Push changes back to Knock
- Work with specific resource types
-
Follow workflow and template guidelines (
rules/workflow-templates.md)- Understand template modes and structures
- Avoid common mistakes with file paths and variables
- Follow best practices for workflow modifications
For managing guides and message types
When working with in-app guides (banners, modals, announcements):
- Start with guides and message types (
rules/guides-and-message-types.md)- Understand that guides are separate from workflows (lifecycle messaging vs notifications)
- Message types define the schema; guides reference them via
schema_keyandschema_variant_key - Use built-in types (banner, modal, card) when possible; create custom message types when needed
What ships with it
6 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.
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 def1d221d7e5
- 4d ago First seen · 171 lines · 27 tokens per session scan A 54edf939e172
knock-cli is a skill published in the GitHub repository knocklabs/skills (0 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 1,908 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…