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.
npx agentmods add commands/ch-bas/kibana-plugin-helper/routegit clone --depth 1 https://github.com/ch-bas/kibana-plugin-helperWrote 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/ch-bas/kibana-plugin-helper/route)<a href="https://agentmods.dev/commands/ch-bas/kibana-plugin-helper/route"><img src="https://agentmods.dev/badge/commands/ch-bas/kibana-plugin-helper/route.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 | $0.00032 | $0.01447 |
| Opus 5 | $0.00016 | $0.00724 |
| Sonnet 5 | $0.00006 | $0.00289 |
| Haiku 4.5 | $0.00003 | $0.00145 |
Grade A, and why
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 4d 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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Server Route
Create a server-side route for your Kibana plugin. Ask the user for:
- HTTP method: GET, POST, PUT, DELETE, PATCH
- Route path: e.g.,
/api/my_plugin/itemsor/api/my_plugin/items/{id} - What it does: Brief description
- Request parameters:
- Path params (from URL, e.g.,
{id}) - Query params (e.g.,
?page=1&perPage=20) - Body (for POST/PUT/PATCH)
- Path params (from URL, e.g.,
- Response: What it returns
- Needs authentication? (default: yes)
- Data source: Elasticsearch, Saved Objects, or external API
Route Template
import { schema } from '@kbn/config-schema';
import type { IRouter } from '@kbn/core/server';
export function register{RouteName}Route(router: IRouter) {
router.{method}(
{
path: '{route_path}',
options: {
tags: ['access:{plugin_id}'],
},
validate: {
params: schema.object({
// Path parameters
id: schema.string(),
}),
query: schema.object({
// Query parameters
page: schema.number({ defaultValue: 1, min: 1 }),
perPage: schema.number({ defaultValue: 20, min: 1, max: 100 }),
search: schema.maybe(schema.string()),
}),
body: schema.object({
// Body parameters (POST/PUT/PATCH)
name: schema.string({ minLength: 1, maxLength: 255 }),
enabled: schema.boolean({ defaultValue: true }),
}),
},
},
async (context, request, response) => {
try {
const coreContext = await context.core;
const { id } = request.params;
const { page, perPage, search } = request.query;
const { name, enabled } = request.body;
// Implementation here
return response.ok({
body: {
// Response data
},
});
} catch (error) {
// Error handling
if (error.output?.statusCode === 404) {
return response.notFound({
body: { message: error.message },
});
}
return response.customError({
statusCode: error.output?.statusCode || 500,
body: { message: error.message },
});
}
}
);
}
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.
- 4d ago First seen · 227 lines · 32 tokens per session scan A 0d293278925c
route is a command published in the GitHub repository ch-bas/kibana-plugin-helper (3 stars, last pushed 6mo ago), licensed MIT. It adds 32 tokens to every session and 1,447 once invoked, about $0.0002 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.
Other commands, from other repositories
dead-code-scan
Scan for dead code, unused imports, duplicates, and zombie code across the project.
dead-code-clean
Actively find and remove dead code, unused imports, duplicates, and zombie code.
esp-teach
One-time project setup -- discover hardware, find datasheets, persist context to CLAUDE.md.
swift-critique
Critique SwiftUI code for patterns, design, clean code, accessibility, and performance.
dotnet-harden
Scan and harden .NET backend code against high-impact anti-patterns such as sync-over-async, lifetime bugs, fat endpoints, and fragile SignalR state.
rust-critique
Deep code critique — read the target Rust code and apply the full review process. Evaluates soundness, ownership, error handling, type design, async correctness, performance, and architecture. Think like a senior Rust engineer giving honest feedback.