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 mark3labs/kit --skill kit-extensionsgit clone --depth 1 https://github.com/mark3labs/kitWrote 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/mark3labs/kit/kit-extensions)<a href="https://agentmods.dev/skills/mark3labs/kit/kit-extensions"><img src="https://agentmods.dev/badge/skills/mark3labs/kit/kit-extensions/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/mark3labs/kit/kit-extensions"><img src="https://agentmods.dev/badge/skills/mark3labs/kit/kit-extensions.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.00053 | $0.02286 |
| Opus 5.5 | $0.00021 | $0.00914 |
| Sonnet 5.5 | $0.00011 | $0.00457 |
| Haiku 4.5 | $0.00005 | $0.00229 |
Grade A, and why
kit-extensions 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 3d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kit Extensions Development Guide
Kit extensions are single-file Go programs interpreted at runtime by Yaegi. They hook into Kit's lifecycle, register custom tools and slash commands, display widgets, intercept editor input, render tool output, register and switch color themes, and more.
Extensions can be distributed via git repositories using kit install. Repos can contain single extensions or collections of multiple extensions.
This file is the entry point. It gives the structure, a minimal example, and the constraints you must never miss. Detailed material lives in the references/ directory (see Reference files below). Read only the reference files that apply to your task.
Extension Structure
Every extension must export a package main with an Init(api ext.API) function:
//go:build ignore
package main
import "kit/ext"
func Init(api ext.API) {
// Register event handlers, tools, commands, etc.
}
The //go:build ignore tag prevents go build from compiling the file directly.
Extension Locations
Extensions are auto-loaded from these directories:
/usr/share/kit/extensions/*.go(system-wide, single files)/usr/share/kit/extensions/*/main.go(system-wide, subdirectories)~/.config/kit/extensions/*.go(user, single files)~/.config/kit/extensions/*/main.go(user, subdirectories).kit/extensions/*.go(project-local, single files).kit/extensions/*/main.go(project-local, subdirectories)
Or loaded explicitly:
kit -e path/to/extension.go
kit --extension path/to/extension.go
Import Path
Extensions import the Kit API as "kit/ext". The full standard library is available plus os/exec for subprocess spawning.
API Overview
The Init function receives an ext.API object for registering handlers, and event handlers receive an ext.Context with runtime capabilities.
api.On*— subscribe to one of 31 lifecycle events (OnSessionStart,OnToolCall,OnAgentEnd, ...). Seereferences/lifecycle-events.md.api.RegisterTool/RegisterCommand/RegisterShortcut/RegisterOption— add LLM tools,/slashcommands, key bindings, and config options. Seereferences/tools-commands-shortcuts.md.ctx.*— runtime capabilities: print output, inject messages, widgets, header/footer, prompts, overlays, editor interceptor, session data/state, model and tool management, LLM completions, themes. Seereferences/context-api.md.api.RegisterToolRenderer/api.RegisterMessageRenderer— custom rendering of tool calls and messages. Seereferences/renderers.md.
What ships with it
9 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.
- references/bridged-sdk-apis.md 5.4 KB
- references/common-patterns.md 8.8 KB
- references/context-api.md 14 KB
- references/lifecycle-events.md 11 KB
- references/plan-mode-example.md 2.2 KB
- references/renderers.md 1.2 KB
- references/testing-and-distribution.md 6.0 KB
- references/tools-commands-shortcuts.md 3.8 KB
- references/yaegi-constraints.md 2.6 KB
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.
- 3d ago Changed 5aa2111f7ac2
- 14d ago Changed d13038d66ea7
- 1mo ago Changed · -1,410 lines scan D → A aaaf8bc41649
- 1mo ago Changed · +29 lines 1483af53b6c8
- 1mo ago First seen · 1,570 lines · 53 tokens per session scan D 7d61e88721d7
kit-extensions is a skill published in the GitHub repository mark3labs/kit (144 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 2,286 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-30.
Other skills, from other repositories
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…
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…
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…