add-route

add-route is a command for Claude Code from naporin0624/claude-plugin-hono-electron. It costs 11 tokens per session (1,324 once invoked), scanned A, original, MIT.

A generator for an Hono route, an HTTP-style endpoint used for communication between an Electron app’s main and renderer processes. It adds Zod schemas so request data can be checked against defined rules.

In plain words
What is it for?
It is for adding a named route with handlers for requests such as listing items or retrieving one item by ID, plus request validation.
Why use it?
It reduces boilerplate and helps keep new routes in the project’s expected location and format.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: positional $N argument.

Part of the hono-electron-ipc plugin — 6 skills, 7 commands shipped together

Good fit It is for adding a named route with handlers for requests such as listing items or retrieving one item by ID, plus request validation.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/naporin0624/claude-plugin-hono-electron/add-route
Install

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.

Clone the repo
git clone --depth 1 https://github.com/naporin0624/claude-plugin-hono-electron

Made for: Claude Code.

Or install hono-electron-ipc, the plugin that ships this one along with the rest of its 6 skills, 7 commands.

Wrote 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.

agentmods badge for add-route

README.md
[![agentmods](https://agentmods.dev/badge/commands/naporin0624/claude-plugin-hono-electron/add-route/github.svg)](https://agentmods.dev/commands/naporin0624/claude-plugin-hono-electron/add-route)
Your own site
<a href="https://agentmods.dev/commands/naporin0624/claude-plugin-hono-electron/add-route"><img src="https://agentmods.dev/badge/commands/naporin0624/claude-plugin-hono-electron/add-route/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.

agentmods 80×15 button for add-route

Your own site · 80×15
<a href="https://agentmods.dev/commands/naporin0624/claude-plugin-hono-electron/add-route"><img src="https://agentmods.dev/badge/commands/naporin0624/claude-plugin-hono-electron/add-route.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,324 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00011 $0.01324
Opus 5 $0.00005 $0.00662
Sonnet 5 $0.00002 $0.00265
Haiku 4.5 $0.00001 $0.00132

Measured 12d ago against content hash bbf6bf2b9a3b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

add-route 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 12d 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.

commands/add-route.md · 195 lines

How it starts

The opening of the file, as written. The whole thing — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Add New Hono IPC Route

Generate a new route for Hono-based IPC with proper structure and Zod validation.

Arguments

  • $1 (required): Route name in kebab-case (e.g., users, auth, event-logs)

Steps

1. Determine Route Location

Find the shared callable directory:

  • Look for src/shared/callable/ directory
  • If not found, check for alternative structures

2. Create Route File

Create src/shared/callable/{route-name}/index.ts:

import { zValidator } from '@hono/zod-validator';
import { Hono } from 'hono';
import { z } from 'zod';

import type { HonoEnv } from '@shared/callable';

const app = new Hono<HonoEnv>();

// Define Zod schemas for request validation
// Example: const CreateItemBody = z.object({ name: z.string(), value: z.number() });

// Define route handlers
export const routes = app
  // GET /{route-name}
  .get('/', (c) => {
    // Access services via c.var.services
    // Example: return c.var.services.{service}.list()
    return c.json({ message: 'List items' }, 200);
  })

  // GET /{route-name}/:id
  .get('/:id', (c) => {
    const id = c.req.param('id');
    // Example: return c.var.services.{service}.get(id)
    return c.json({ id, message: 'Get item' }, 200);
  })

  // POST /{route-name}
  // .post('/', zValidator('json', CreateItemBody), (c) => {
  //   const body = c.req.valid('json');
  //   // Example: return c.var.services.{service}.create(body)
  //   return c.json({ message: 'Created' }, 201);
  // })

  // PUT /{route-name}/:id
  // .put('/:id', zValidator('json', UpdateItemBody), (c) => {
  //   const id = c.req.param('id');
  //   const body = c.req.valid('json');
  //   // Example: return c.var.services.{service}.update(id, body)
  //   return c.json({ message: 'Updated' }, 200);
  // })

  // DELETE /{route-name}/:id
  // .delete('/:id', (c) => {
  //   const id = c.req.param('id');
  //   // Example: return c.var.services.{service}.delete(id)
  //   return c.json({ message: 'Deleted' }, 200);
  // });

Read the full file on GitHub · 195 lines

Changes

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.

  1. 12d ago First seen · 195 lines · 11 tokens per session scan A bbf6bf2b9a3b

Subscribe to this mod's changes

add-route 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,324 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-31.