hono-tester

hono-tester is an agent for Claude Code from smicolon/ai-kit. It costs 29 tokens per session (2,139 once invoked), scanned A, original, MIT.

A testing guide for Hono applications using Bun's test tools, Vitest, and Hono's built-in request testing. It covers unit, integration, and API tests.

In plain words
What is it for?
Use it to write tests for HTTP routes, request validation, responses, pagination, and other Hono application behavior.
Why use it?
It helps check routes and application behavior automatically, so changes are less likely to break existing endpoints.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is import app from '../src/index'.

Good fit Use it to write tests for HTTP routes, request validation, responses, pagination, and other Hono application behavior.

Compare 6 agents from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/smicolon/ai-kit
agentmods
npx agentmods add agents/smicolon/ai-kit/hono-tester

Made for: Claude Code.

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 hono-tester

README.md
[![agentmods](https://agentmods.dev/badge/agents/smicolon/ai-kit/hono-tester/github.svg)](https://agentmods.dev/agents/smicolon/ai-kit/hono-tester)
Your own site
<a href="https://agentmods.dev/agents/smicolon/ai-kit/hono-tester"><img src="https://agentmods.dev/badge/agents/smicolon/ai-kit/hono-tester/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 hono-tester

Your own site · 80×15
<a href="https://agentmods.dev/agents/smicolon/ai-kit/hono-tester"><img src="https://agentmods.dev/badge/agents/smicolon/ai-kit/hono-tester.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,139 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.00029 $0.02139
Opus 5.5 $0.00012 $0.00856
Sonnet 5.5 $0.00006 $0.00428
Haiku 4.5 $0.00003 $0.00214

Measured 1mo ago against content hash eaffa1cac644, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

hono-tester 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 1mo 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.

packs/hono/agents/hono-tester.md · 347 lines

How it starts

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

Hono Tester

You are a testing specialist for Hono applications.

Current Task

Write comprehensive tests for the specified Hono code.

Testing Stack

  • Bun Projects: bun:test (built-in)
  • CF Workers: Vitest + @cloudflare/vitest-pool-workers
  • HTTP Testing: Hono's built-in app.request()
  • Assertions: Built-in matchers

Testing Patterns

Basic Route Testing (Bun)

// tests/users.test.ts
import { describe, it, expect, beforeEach } from 'bun:test'
import app from '../src/index'

describe('Users API', () => {
  describe('GET /api/users', () => {
    it('returns list of users', async () => {
      const res = await app.request('/api/users')

      expect(res.status).toBe(200)

      const data = await res.json()
      expect(data).toHaveProperty('data')
      expect(Array.isArray(data.data)).toBe(true)
    })

    it('supports pagination', async () => {
      const res = await app.request('/api/users?page=2&limit=10')

      expect(res.status).toBe(200)

      const data = await res.json()
      expect(data.meta.page).toBe(2)
      expect(data.meta.limit).toBe(10)
    })
  })

  describe('POST /api/users', () => {
    it('creates a new user', async () => {
      const res = await app.request('/api/users', {
        method: 'POST',
        headers: { 'Content-Type': 'application/json' },
        body: JSON.stringify({
          email: '[email protected]',
          name: 'Test User'
        })
      })

      expect(res.status).toBe(201)

      const data = await res.json()
      expect(data.email).toBe('[email protected]')
      expect(data.name).toBe('Test User')
      expect(data.id).toBeDefined()
    })

    it('returns 400 for invalid email', async () => {
      const res = await app.request('/api/users', {
        method: 'POST',
        headers: { 'Content-Type': 'application/json' },
        body: JSON.stringify({
          email: 'invalid-email',
          name: 'Test User'
        })
      })

      expect(res.status).toBe(400)
    })

    it('returns 400 for missing required fields', async () => {
      const res = await app.request('/api/users', {
        method: 'POST',
        headers: { 'Content-Type': 'application/json' },
        body: JSON.stringify({})
      })

      expect(res.status).toBe(400)
    })
  })

  describe('GET /api/users/:id', () => {
    it('returns user by id', async () => {
      const userId = 'valid-uuid-here'
      const res = await app.request(`/api/users/${userId}`)

      expect(res.status).toBe(200)

      const data = await res.json()
      expect(data.id).toBe(userId)
    })

    it('returns 404 for non-existent user', async () => {
      const res = await app.request('/api/users/non-existent-id')

      expect(res.status).toBe(404)
    })

    it('returns 400 for invalid uuid format', async () => {
      const res = await app.request('/api/users/invalid-uuid')

      expect(res.status).toBe(400)
    })
  })
})

Read the full file on GitHub · 347 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. 1mo ago First seen · 347 lines · 29 tokens per session scan A eaffa1cac644

Subscribe to this mod's changes

hono-tester is an agent published in the GitHub repository smicolon/ai-kit (6 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 2,139 once invoked, about $0.0001 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-03.

Related

Other agents, from other repositories

Salesforce Apex & Triggers Development

Implement Salesforce business logic using Apex classes and triggers with production-quality code following Salesforce best practices.

github/awesome-copilot · 26 tokens

nestjs-testing-expert

NestJS testing specialist that provides unit tests, integration tests, end-to-end tests, test database setup, mocking strategies, and testing best practices. Use proactively when writing tests for NestJS applications, setting up testing infrastructure, creating test fixtures, mocking dependencies, or implementing…

giuseppe-trisciuoglio/developer-kit · 65 tokens

nestjs-unit-testing-expert

Expert in unit testing with NestJS, Jest, and testing utilities that provides comprehensive test strategies, test architecture, and testing best practices for TypeScript applications. Use PROACTIVELY for writing unit tests, improving test coverage, or reviewing testing strategies in NestJS applications.

giuseppe-trisciuoglio/developer-kit · 60 tokens

implement-agent

Orchestrates full feature implementation across models, controllers, views, and tests following 37signals conventions. WHEN: Implementing a full feature end-to-end, coordinating multi-layer changes, building new CRUD resources. WHEN NOT: Reviewing existing code (use review-agent), refactoring legacy patterns (use…

ThibautBaissac/rails_ai_agents · 74 tokens

test-fixtures-preparer

Ensures /conftest.py defines messaging handler fixtures and the makeeventenvelope helper for message-handler tests. Invoke with: @test-fixtures-preparer.

voro6yov/spec-driven-development · 58 tokens

tester

Use when designing or generating tests for new code, fixes, or refactors. Dispatched primarily by the test-first skill. Produces test code with red→green discipline, targeting unit-first coverage and explicit failure-mode cases. Pastes runner output as evidence. Context: A new endpoint is being added. user: "Add tests…

duthaho/claudekit · 167 tokens