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/qxbyte/pluginhub/specnpx skills add qxbyte/pluginhub --skill specgit clone --depth 1 https://github.com/qxbyte/pluginhubWhat 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.00100 | $0.05109 |
| Opus 5 | $0.00050 | $0.02554 |
| Sonnet 5 | $0.00020 | $0.01022 |
| Haiku 4.5 | $0.00010 | $0.00511 |
Grade A, and why
spec 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.
How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/specode:spec — create a new spec (orchestration shell)
Host-tool convention 🔧: tool names in this skill —
AskUserQuestion(structured multiple-choice question), theSkilltool (invoke another skill by name),Agent/Task(dispatch a subagent) — are written for Claude-family hosts (Claude Code / CodeBuddy), where naming them directly is the most reliable. On a host that lacks one, use its nearest equivalent (a structured-question tool / a skill-invocation mechanism / a subagent-dispatch tool); with no equivalent, fall back to plain-text prose / reading the target skill'sSKILL.mddirectly / sequential single-agent execution. The described behavior is what matters, not the exact tool name.
specode is no longer a state machine. It is an orchestration shell that handles only its own distinctive value: the spec lifecycle, fixed on-disk artifacts, "documents-as-state" phase inference, and handing the execution tail (the 执行方式 selector → execution → acceptance, including the task-swarm handoff bridge) to the sibling specode:execute skill. The heavy lifting (clarification, design, TDD execution, acceptance) is done by autonomously calling superpowers skills in the matching phase; when superpowers is absent, specode-native fallback takes over. There is no persistent session file, no multi-window locking, no spec config file, no status-summary footer line, no forced code-doc sync nagging, and no session log collection.
Activation Guard
Activate only when the current user input is /specode:spec <request>, or the user explicitly asks to start a new spec ("use spec mode" / "按 spec 流程做" / equivalent, together with a fresh requirement). Otherwise do not activate; handle as normal conversation. (Resuming an existing spec is the sibling /specode:continue skill; listing is /specode:list.)
There is no session file — whether a spec is active is inferred entirely from the current conversation context (which slug is running this turn) plus the documents under <specsRoot>/<slug>/. No persistent state file is ever read.
What ships with it
6 files 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 · 132 lines · 100 tokens per session scan A 3003aee2c0c8
spec is a skill published in the GitHub repository qxbyte/pluginhub (3 stars, last pushed 27d ago), licensed MIT. It adds 100 tokens to every session and 5,109 once invoked, about $0.0005 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
douyin-favorites-to-knowledge
将用户已授权账号中的抖音视频收藏或用户明确指定的喜欢列表配置并同步到本地 Markdown 或 Obsidian 知识库；默认收藏，只有用户明确说喜欢/点赞才切换来源。首次明确选择推荐的 SiliconFlow转录、本地 Whisper 或不转录。不得绕过登录、访问他人账号或泄露 Cookie 与私密数据。.
knowledge-extractor
Entrevista a un experto de dominio (SME) para extraer su conocimiento técnico tácito y sintetizarlo en una Skill reutilizable. Se activa PROACTIVAMENTE ante 3 situaciones: (1) Frustración — el usuario se queja de código, arquitectura o falta de estándares; (2) Ambigüedad sin Reglas — se pide un refactor profundo pero…
MCP Developer
Skill para desarrollar, mantener y extender el servidor MCP de Obsidian. Incluye patrones de código, arquitectura, testing y gestión de paquetes.
Python Patterns
Buenas prácticas y patrones de desarrollo Python para el proyecto MCP. Incluye estándares de código, patrones arquitectónicos, y convenciones.
Refactoring
Guía para refactorizar código Python de forma segura y efectiva. Incluye técnicas de refactoring, detección de code smells, y mejoras.
Documentation Updater
Skill para mantener la documentación sincronizada con el código. Incluye patrones de documentación, ubicaciones estándar, y checklists.