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-pluginnpx skills add voidvec/drogon-claude-plugin --skill drogon-gen-plugingit 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.00035 | $0.00396 |
| Opus 5 | $0.00017 | $0.00198 |
| Sonnet 5 | $0.00007 | $0.00079 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
drogon-gen-plugin 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 yesterday.
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-plugin
生成 drogon Plugin（系统级扩展）类及配置声明。
使用场景
当需要系统级扩展（连接池、第三方 SDK 初始化、全局资源管理）时，使用此技能生成符合 drogon 约定的 Plugin 代码。Plugin 在 app().run() 之前同步初始化，整个应用生命周期内单实例存在。
与 Filter / Middleware 的区别：Plugin 不处理请求，负责应用级初始化与资源管理；Filter 做请求拦截，Middleware 做全局处理链。三者职责不得混用。
输入参数
plugin_name: Plugin class name (required)purpose: 用途描述（如redis_pool、sdk_init）config_keys: 配置项（从config.json的plugins数组读取的键，格式key:type）
输出
- Plugin 类头文件（继承
drogon::Plugin<ClassName>） initAndStart(const Json::Value &config)/shutdown()实现config.json的plugins数组声明片段- 获取插件实例的代码：
app().getPlugin<ClassName>()
示例
/drogon-gen-plugin plugin_name=RedisPool purpose=redis_pool config_keys=max_connections:int,timeout:double
生成 Redis 连接池 Plugin。
参考文件
详细实现指南见 references/code-guide.md（含 Plugin 规范、三者职责边界对比、禁止模式清单）。生成代码前先读取该文件。
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.
- yesterday First seen · 41 lines · 35 tokens per session scan A 09452a68a000
drogon-gen-plugin is a skill published in the GitHub repository voidvec/drogon-claude-plugin (1 stars, last pushed 5d ago), licensed MIT. It adds 35 tokens to every session and 396 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
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.
mmr
Run multi-model code review with the MMR CLI (mmr review) before merging or finishing a change, or a multi-model design critique (mmr critique) of a design doc, plan, or proposed approach before building it. Use when the user asks to review code, a PR, a diff, or staged changes, or to critique/second-opinion a design…
commands-standards
Standards for authoring SDD plugin commands — frontmatter, user interaction, skill/agent invocation, CLI integration, and output formatting.