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 skills/voidvec/drogon-claude-plugin/drogon-gen-coroutine-handlernpx skills add voidvec/drogon-claude-plugin --skill drogon-gen-coroutine-handlergit clone --depth 1 https://github.com/voidvec/drogon-claude-pluginWhat 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.00048 | $0.00376 |
| Opus 5 | $0.00024 | $0.00188 |
| Sonnet 5 | $0.00010 | $0.00075 |
| Haiku 4.5 | $0.00005 | $0.00038 |
Grade A, and why
drogon-gen-coroutine-handler 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 2d 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.
What it actually says
drogon-gen-coroutine-handler
生成 drogon 协程代码：handler、协程中间件（HttpCoroMiddleware）、协程 ORM/Redis/HttpClient 调用。
使用场景
当项目已启用协程（USE_COROUTINE=ON）且需编写异步 handler / 中间件时使用。
输入参数
kind:handler/middleware/orm_call/http_callreturn_type: handler 的返回类型（Task<HttpResponsePtr>/AsyncTask），仅kind=handler时有效class_name: 类名（仅kind=middleware）
输出
- 协程代码（正确的返回类型、
co_await、try/catch 兜底） - 参数按值传递（裸 handler）或可引用（协程中间件，框架已拷贝）
- AsyncTask 的 try/catch 提醒（否则未处理异常
std::terminate）
示例
/drogon-gen-coroutine-handler kind=handler return_type=Task<HttpResponsePtr>
/drogon-gen-coroutine-handler kind=middleware class_name=AuthMiddleware
参考文件
详细实现指南见 references/code-guide.md（含返回类型对照、参数生命周期对照、代码模板、禁止模式）。生成代码前先读取该文件。
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 36 lines · 48 tokens per session scan A 934c7106fbdc
drogon-gen-coroutine-handler is a skill published in the GitHub repository voidvec/drogon-claude-plugin (1 stars, last pushed 5d ago), licensed MIT. It adds 48 tokens to every session and 376 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 skills, from other repositories
cgo-bindings
cgo conventions for linking Go to a C or Rust static library: import "C" directives, type/string conversion, CString memory management, thread safety, and Go pointer pinning. Load when generating or reviewing cgo bindings that call a C or Rust core from Go.
arduino-code-generator
Generate Arduino and embedded C++ snippets for sensors, actuators, buses, state machines, timing, data logging, and hardware abstraction. Use when a user requests implementation code and provide the exact board, framework, toolchain, pins, voltage, memory, and library versions first. Bundled templates target UNO…
scaffold-runner
Interactive wrapper for the scaffold CLI that surfaces a pipeline step's decision points before executing it and manages the step lifecycle. Use when the user asks to run a scaffold step ("run scaffold ", "scaffold ", "what's next?"), to start building, or works in a project with a .scaffold/ directory.
work-beads
Work the project's Beads task queue end-to-end - claim a bead, build in an isolated worktree, verify, review, merge, close, report. Use when the user says "/work-beads", "/work-beads 5", "work the next N beads", "work on ", "pick up some open tasks", or asks to work the backlog. Applies to every coding agent (Claude…
scaffold-pipeline
Static reference for scaffold pipeline ordering, dependencies, and phase structure. Use ONLY for questions about pipeline design, step ordering, or dependency constraints — NOT for status, progress, or "what's next" queries (those go through scaffold-runner).
multi-model-dispatch
Correct patterns for invoking Codex CLI and Antigravity CLI (agy) as independent reviewers from Claude Code. Covers headless invocation, context bundling, output parsing, dual-model reconciliation, and fallback handling.