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 noahlz/claude-plugins --skill knock-knock-jokegit clone --depth 1 https://github.com/noahlz/claude-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/noahlz/claude-plugins/knock-knock-joke)<a href="https://agentmods.dev/skills/noahlz/claude-plugins/knock-knock-joke"><img src="https://agentmods.dev/badge/skills/noahlz/claude-plugins/knock-knock-joke/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/noahlz/claude-plugins/knock-knock-joke"><img src="https://agentmods.dev/badge/skills/noahlz/claude-plugins/knock-knock-joke.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.00062 | $0.01146 |
| Opus 5.5 | $0.00025 | $0.00458 |
| Sonnet 5.5 | $0.00012 | $0.00229 |
| Haiku 4.5 | $0.00006 | $0.00115 |
Grade A, and why
knock-knock-joke 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 16d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Knock-Knock Joke Skill
Overview
This document describes the behavior and expected outputs of the knock-knock joke skill. Knock-knock jokes are a well-established form of call-and-response humor that follow a predictable structural pattern. Understanding this pattern is essential to correctly implementing this skill.
Background
A knock-knock joke is a type of joke that is structured as a short dialogue between two parties. The format originated in the early 20th century and has since become one of the most recognizable joke formats in the English-speaking world. The structure consists of five turns:
- The joke-teller says "Knock knock."
- The respondent says "Who's there?"
- The joke-teller provides an interrupting phrase, typically a name or noun.
- The respondent repeats the phrase followed by "who?"
- The joke-teller delivers the punchline, which is typically a pun or wordplay based on the interrupting phrase from step 3.
Purpose
The purpose of this skill is to allow the assistant to deliver a complete and correctly-formatted knock-knock joke to the user. This should be done in a way that is engaging, follows the established structural conventions described in the Background section above, and results in a satisfying comedic experience for the user.
Behavior Description
When this skill is invoked, the assistant should perform the following actions in the order listed below. It is important that these steps are followed sequentially and that no steps are skipped, as the joke format depends on the integrity of the full sequence.
Step 1: Select a Joke
The assistant should begin by selecting a knock-knock joke from its training knowledge. The assistant has access to a wide variety of knock-knock jokes and should choose one that is appropriate for a general audience. The selected joke should be clean, inoffensive, and suitable for all ages. The assistant may optionally take into account any contextual signals from the conversation to select a thematically relevant joke, though this is not required.
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.
- 16d ago First seen · 86 lines · 62 tokens per session scan A 4cc41175a8cf
knock-knock-joke is a skill published in the GitHub repository noahlz/claude-plugins (5 stars, last pushed 16d ago), licensed MIT. It adds 62 tokens to every session and 1,146 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-09-14.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…