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 skills add louisbrulenaudet/monorepo-template --skill review-honogit clone --depth 1 https://github.com/louisbrulenaudet/monorepo-templateWrote 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/skills/louisbrulenaudet/monorepo-template/review-hono)<a href="https://agentmods.dev/skills/louisbrulenaudet/monorepo-template/review-hono"><img src="https://agentmods.dev/badge/skills/louisbrulenaudet/monorepo-template/review-hono/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.
<a href="https://agentmods.dev/skills/louisbrulenaudet/monorepo-template/review-hono"><img src="https://agentmods.dev/badge/skills/louisbrulenaudet/monorepo-template/review-hono.svg" alt="Reviewed on agentmods" width="80" 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.00066 | $0.00926 |
| Opus 5 | $0.00033 | $0.00463 |
| Sonnet 5 | $0.00013 | $0.00185 |
| Haiku 4.5 | $0.00007 | $0.00093 |
Grade A, and why
review-hono 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.
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Hono
Review the Hono usage in worker-api (and any future HTTP-surface workers) for alignment with current official Hono best practices on Cloudflare Workers - routing structure, middleware composition, validation, and developer experience. Your reply must be a plan of suggested changes: concise, actionable, structured - not only prose.
Invocation
Text after the slash command is additional scope/focus (e.g. "middleware", "error handling") - narrow the review accordingly.
Ground truth (mandatory)
Your pre-trained knowledge of Hono may be outdated. Do not draft suggestions from memory alone.
- Resolve "Hono" via the Context7 MCP (
resolve-library-id→query-docs): routing patterns, middleware ordering semantics, validators/Zod integration helpers, error handling (HTTPException,onError), Cloudflare Workers adapters/helpers, RPC/hcclient typing if referenced. - For anything Context7 lacks, use Firecrawl search/scrape restricted to the official domain (
hono.dev) - guides and API reference pages relevant to findings. - Version currency: catalog
honoin pnpm-workspace.yaml and installed version vs latest stable changelog; flag deprecated APIs used in code (e.g. old validator helpers). - Cite the retrieved source next to every finding; label anything unverifiable as Unverified.
Scope artifacts
- apps/worker-api/src/index.ts and apps/worker-api/src/routes/
- Contracts in packages/dtos-common/ (
api/, Zod schemas at boundaries) - Correlation-id middleware wiring (packages/correlation-id,
X-Request-Id) - apps/worker-api/AGENTS.md; CORS/body-limit/security middleware configuration
- Tests exercising routes under
apps/worker-api/tests/
Analysis axes
- Routing structure: feature routers composed under a minimal
index.tsper repo convention; path naming consistent; 404/not-found handling explicit. - Middleware order: global-first ordering (request-id → CORS → body limits → routes → error handler) verified against current Hono semantics; async middleware awaited (no floating promises).
- Validation: every route validates input/output with Zod schemas from
@repo/dtos-common; no ad-hoc parsing at boundaries; status codes typed correctly. - Error handling: centralized
onError/HTTPExceptionpattern; safe error responses (no internals leaked); consistent JSON error envelope. - Workers fit: edge-safe usage (no Node-only APIs); streaming responses handled correctly where present; no blocking work on hot paths.
- Version currency: deprecated helpers replaced; new built-in middleware adopted where it removes hand-rolled code.
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.
- 12d ago First seen · 63 lines · 66 tokens per session scan A 3818196e3ad3
review-hono is a skill published in the GitHub repository louisbrulenaudet/monorepo-template (19 stars, last pushed 11d ago), licensed Apache-2.0. It adds 66 tokens to every session and 926 once invoked, about $0.0003 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-30.
Other skills, from other repositories
sdd-apply
Skill "sdd-apply" from Gentleman-Programming/gentle-ai, covering execution role, language domain contract, purpose, what you receive and execution and persistence contract.
bfl-api
BFL FLUX API integration guide covering endpoints, async polling patterns, rate limiting, error handling, webhooks, and regional endpoints with Python and TypeScript code examples.
api-design-reviewer
Use when reviewing API designs for consistency, usability, versioning, error semantics, security, backward compatibility, and developer experience before implementation or release.
kafka-connector-review
Review Kafka Connect connector configurations for common misconfigurations using the Lenses MCP server. Checks error handling, DLQ setup, converters, transforms, task count and task health. Use when user says "review connectors", "check connector configs", "why is my connector failing" or asks about Kafka Connect…
kafka-dlq-review
Review dead letter queue implementations for completeness using the Lenses MCP server. Checks DLQ topic existence, configuration, monitoring, metadata preservation, retry logic, reprocessing paths and connector DLQ alignment. Use when user says "review dead letter queues", "check DLQ setup", "DLQ audit" or asks about…
kafka-perf-review
Review Kafka producer and consumer performance configurations in both the live cluster (via Lenses MCP) and the codebase. Flags un-tuned defaults, anti-patterns and missing best practices. Use when user says "review Kafka performance", "check producer configs", "tune Kafka settings" or asks about throughput, batching…