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/naporin0624/claude-plugin-hono-electronWrote 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/naporin0624/claude-plugin-hono-electron/check)<a href="https://agentmods.dev/commands/naporin0624/claude-plugin-hono-electron/check"><img src="https://agentmods.dev/badge/commands/naporin0624/claude-plugin-hono-electron/check/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/commands/naporin0624/claude-plugin-hono-electron/check"><img src="https://agentmods.dev/badge/commands/naporin0624/claude-plugin-hono-electron/check.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.00009 | $0.00745 |
| Opus 5 | $0.00005 | $0.00373 |
| Sonnet 5 | $0.00002 | $0.00149 |
| Haiku 4.5 | $0.00001 | $0.00075 |
Grade A, and why
check 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 9d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check Project Patterns
Validate the entire project against established architecture patterns and best practices.
Arguments
--fix: Suggest or apply fixes for detected issues--focus=<category>: Check only specific category (structure, cqrs, routes, atoms, ipc, errors)
Validation Categories
| Category | Checks |
|---|---|
structure |
Directory structure, file naming conventions |
cqrs |
Query returns Observable<T>, Command returns ResultAsync<void, Error> |
routes |
Hono route patterns, Zod validation usage |
atoms |
Jotai hybrid atom patterns, non-async selectors |
ipc |
IPC communication patterns, timeout handling |
errors |
Error boundaries, Result pattern matching |
Critical Checks
Timeout in firstValueFrom (HIGH PRIORITY)
Problem: firstValueFrom() without timeout() can hang indefinitely.
// BAD - No timeout, can hang forever
const data = await firstValueFrom(service.list());
// GOOD - Has timeout with proper error handling
import { timeout, TimeoutError } from 'rxjs';
const data = await firstValueFrom(
service.list().pipe(timeout(5000))
).catch((e) => {
if (e instanceof TimeoutError) {
throw new ApplicationError('Service timeout');
}
throw e;
});
Pattern to search: firstValueFrom without adjacent timeout
Hybrid Atom Async Getter (MEDIUM)
// BAD - async getter causes Suspense issues
export const usersAtom = atom(async (get) => { ... });
// GOOD - sync getter with conditional
export const usersAtom = atom((get) => {
const stream = get(streamAtom);
return stream !== undefined ? stream.value : get(singleFetchAtom);
});
Validation Workflow
1. Run glob/grep to find relevant files
2. Check each file against patterns
3. Report findings with file:line references
4. Optionally suggest fixes
Output Format
/check results:
Directory Structure
[PASS] src/shared/callable/ exists
[PASS] src/main/services/ exists
CQRS Services
[PASS] UserService follows CQRS pattern
[WARN] EventService.get() should return Observable, found Promise
-> src/main/services/event.service.ts:45
Timeout Handling
[FAIL] Missing timeout() in firstValueFrom
-> src/renderer/src/hooks/useUsers.ts:12
-> src/main/callable/users/index.ts:28
Suggested fix:
service.list().pipe(timeout(5000))
Total: 15 passed, 2 warnings, 1 error
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.
- 9d ago First seen · 118 lines · 0 tokens per session scan A f0a408876da8
check is a command published in the GitHub repository naporin0624/claude-plugin-hono-electron (3 stars, last pushed 7mo ago), licensed MIT. It adds 9 tokens to every session and 745 once invoked, about $0.0000 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
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.