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.
/plugin marketplace add smicolon/ai-kitnpx agentmods add plugins/smicolon/ai-kit/honogit clone --depth 1 https://github.com/smicolon/ai-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/plugins/smicolon/ai-kit/hono)<a href="https://agentmods.dev/plugins/smicolon/ai-kit/hono"><img src="https://agentmods.dev/badge/plugins/smicolon/ai-kit/hono.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
hono 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 yesterday.
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.
What it actually says
{
"name": "hono",
"version": "0.2.1",
"description": "Hono Edge framework standards with 4 agents and 4 auto-enforcing skills including OpenAPI and streaming for Bun and Cloudflare Workers",
"source": "./packs/hono",
"author": {
"name": "Smicolon",
"email": "[email protected]",
"url": "https://github.com/smicolon"
},
"homepage": "https://github.com/smicolon/ai-kit",
"repository": "https://github.com/smicolon/ai-kit",
"license": "MIT",
"category": "backend",
"keywords": [
"hono",
"bun",
"cloudflare-workers",
"edge",
"typescript",
"api",
"rpc",
"openapi"
],
"agents": [
"./agents/hono-architect.md",
"./agents/hono-builder.md",
"./agents/hono-tester.md",
"./agents/hono-reviewer.md"
],
"commands": [
"./commands/route-create.md",
"./commands/middleware-create.md",
"./commands/project-init.md",
"./commands/rpc-client.md"
],
"skills": [
"./skills/hono-patterns",
"./skills/cloudflare-bindings",
"./skills/zod-validation",
"./skills/rpc-typesafe"
]
}What it installs
The manifest is a name and a version. 4 skills travel with it, and installing the plugin installs all of them — 177 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside marketplace.json#hono 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.
- yesterday Changed · +1 lines 701b51cde58f
- yesterday First seen · 42 lines scan A 0b7ce994bfc9
hono is a plugin published in the GitHub repository smicolon/ai-kit (6 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-03.
Other plugins, from other repositories
elastic-observability
Elastic Observability skills - OpenTelemetry instrumentation and migration (.NET, Java, Python), LLM observability, log search, SLOs, and service health.
cybrix-deploy
Deploy the current static site to a live HTTPS URL via Cybrix. Detects Next.js export, Astro, Vite, Hugo, Eleventy, and plain HTML. Returns a live URL on .cbrx.cc in under 60 seconds.
spacelift
Procedural guide and references for working with Spacelift via the spacelift-local MCP - manage stacks, runs, policies, spaces, integrations, and the lifecycle of cloud resources through Intent (OpenTofu/Terraform).
cloud-storage
Cloud storage management with AWS S3 MCP for uploads, backups, and file operations.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
claude-plugins-official marketplace
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.