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/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/commands/smicolon/ai-kit/rpc-client)<a href="https://agentmods.dev/commands/smicolon/ai-kit/rpc-client"><img src="https://agentmods.dev/badge/commands/smicolon/ai-kit/rpc-client.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.00013 | $0.01411 |
| Opus 5 | $0.00006 | $0.00705 |
| Sonnet 5 | $0.00003 | $0.00282 |
| Haiku 4.5 | $0.00001 | $0.00141 |
Grade A, and why
rpc-client 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 — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Hono RPC Client
Create a type-safe client for your Hono API using the hc client.
Workflow
Step 1: Verify Server Setup
Check that the server exports the app type:
// src/index.ts
import { Hono } from 'hono'
const app = new Hono()
// ... routes ...
export default app
// REQUIRED: Export type for RPC client
export type AppType = typeof app
Step 2: Create Client Package
For monorepo or separate client package:
# If using monorepo with workspaces
mkdir -p packages/api-client
cd packages/api-client
bun init -y
bun add hono
packages/api-client/package.json:
{
"name": "@{project}/api-client",
"version": "1.0.0",
"main": "src/index.ts",
"types": "src/index.ts",
"exports": {
".": "./src/index.ts"
},
"dependencies": {
"hono": "^4.0.0"
}
}
Step 3: Create Client
packages/api-client/src/index.ts:
import { hc } from 'hono/client'
import type { AppType } from '@{project}/api/src/index'
// Create typed client
export const createApiClient = (baseUrl: string) => {
return hc<AppType>(baseUrl)
}
// Default client for common use
export const api = createApiClient(
process.env.API_URL || 'http://localhost:8787'
)
// Re-export types for consumers
export type { AppType }
// Export inferred types for convenience
export type ApiClient = ReturnType<typeof createApiClient>
Step 4: Usage Examples
Basic Usage:
import { api } from '@{project}/api-client'
// GET request
const users = await api.api.users.$get()
const data = await users.json()
// POST request with body
const newUser = await api.api.users.$post({
json: {
email: '[email protected]',
name: 'New User'
}
})
// GET with query params
const searchResults = await api.api.users.$get({
query: {
page: 1,
limit: 10,
search: 'john'
}
})
// GET with path params
const user = await api.api.users[':id'].$get({
param: { id: 'user-uuid' }
})
// PUT with params and body
const updated = await api.api.users[':id'].$put({
param: { id: 'user-uuid' },
json: { name: 'Updated Name' }
})
// DELETE
await api.api.users[':id'].$delete({
param: { id: 'user-uuid' }
})
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 First seen · 264 lines · 13 tokens per session scan A 1739a92ba963
rpc-client is a command published in the GitHub repository smicolon/ai-kit (6 stars, last pushed 3d ago), licensed MIT. It adds 13 tokens to every session and 1,411 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-09-03.
Other commands, from other repositories
azure-dotnet-webapp:webapp-setup
Interactive setup wizard for ASP.NET Core Web API or Blazor projects on Azure — selects project type, auth, database, and Graph integration; scaffolds the full project structure with compilable stubs; and verifies the build.
frappe-fullstack
Invoke multiple Frappe agents in parallel for full-stack development - coordinates backend, frontend, and architecture agents for complete feature implementation.
add-table
Create advanced data table component with rich features. Implement column sorting (ascending/descending) with multi-column support. Add pagination with page size selector and jump to page. Implement client-side and server-side filtering. Add column visibility toggle with saved preferences. Implement row selection with…
add-seo
Add comprehensive SEO to a page using Next.js 15 Metadata API.
full-stack-feature
Orchestrate full-stack feature development across backend, frontend, and infrastructure layers with modern API-first approach.
checklist
Generate a custom checklist for the current feature based on user requirements.