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.
git clone --depth 1 https://github.com/naporin0624/claude-plugin-hono-electronWrote 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/commands/naporin0624/claude-plugin-hono-electron/init)<a href="https://agentmods.dev/commands/naporin0624/claude-plugin-hono-electron/init"><img src="https://agentmods.dev/badge/commands/naporin0624/claude-plugin-hono-electron/init.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.1 | $0.00011 | $0.01648 |
| Opus 5 | $0.00005 | $0.00824 |
| Sonnet 5 | $0.00002 | $0.00330 |
| Haiku 4.5 | $0.00001 | $0.00165 |
Grade A, and why
init scanned grade A with 1 finding 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
async fetch(input, init) { How it starts
The opening of the file, as written. The whole thing — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Initialize Hono Electron IPC Architecture
Set up type-safe IPC communication using Hono RPC for this Electron application.
Arguments
$1(optional): Source directory path (default:src)
Prerequisites Check
Before setting up, verify:
- This is an Electron project (check for
electronin package.json) - TypeScript is configured
- Determine package manager (pnpm, npm, or yarn)
Installation Steps
1. Install Dependencies
Install required packages:
# Using detected package manager
pnpm add hono @hono/zod-validator zod
# or
npm install hono @hono/zod-validator zod
2. Create Directory Structure
Create the following directories:
src/
├── shared/
│ └── callable/
│ ├── index.ts # Factory and app creation
│ └── types.d.ts # Type export for client
├── main/
│ └── callable/
│ └── index.ts # Service injection
└── renderer/
└── src/
└── adapters/
└── client.ts # Custom hc client
3. Create Factory File
Create src/shared/callable/index.ts:
import { createFactory } from 'hono/factory';
import { logger } from 'hono/logger';
// Define your services here
// These will be injected from the main process
type Services = {
// Add your service interfaces here
// example: userService: UserService;
};
type Variables = {
services: Services;
};
export type HonoEnv = {
Variables: Variables;
};
type ExternalDependencies = {
services: Services;
};
const factory = (variables: ExternalDependencies) =>
createFactory<HonoEnv>({
initApp(app) {
// Optional: Add request logging
app.use(logger());
// Inject services into Hono context
app.use((c, next) => {
c.set('services', variables.services);
return next();
});
},
});
export const createApp = (...args: Parameters<typeof factory>) => {
return factory(...args).createApp();
// Routes will be registered here using .route()
// Example:
// .route('/users', users.routes)
// .route('/auth', auth.routes)
};
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.
- 8d ago First seen · 261 lines · 11 tokens per session scan A 990c010cd03e
init is a command published in the GitHub repository naporin0624/claude-plugin-hono-electron (3 stars, last pushed 7mo ago), licensed MIT. It adds 11 tokens to every session and 1,648 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
vue3
Apply Vue 3 with TypeScript and Composition API patterns.
svelte:component
Create new Svelte components with best practices, proper structure, and optional TypeScript support.
discover-frontend
Load frontend skills (React, Next.js, TypeScript, state management).
component
Create a new Vue 3 component with TypeScript and Composition API.
electrobun-window
Generate a new BrowserWindow with a matching renderer entry point and type-safe RPC schema connecting them. Usage: /electrobun-window [name].
typescript-scaffold
You are a TypeScript project architecture expert specializing in scaffolding production-ready Node.js and frontend applications. Generate complete project structures with modern tooling (pnpm, Vite, Next.js), type safety, testing setup, and configuration following current best practices.