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/swarmnpx skills add qxbyte/pluginhub --skill swarmgit 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.00074 | $0.02917 |
| Opus 5 | $0.00037 | $0.01458 |
| Sonnet 5 | $0.00015 | $0.00583 |
| Haiku 4.5 | $0.00007 | $0.00292 |
Grade D, and why
swarm scanned grade D with 2 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
> **Host-tool convention** 🔧: this skill orchestrates by dispatching subagents ("fork") and reading their completion status. Mechanism names — the `Task`/`Agent` tool (dispatch a subagent), the `Explore` agent (a read-o Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- **result.md missing STATUS** → re-fork the **same-named** agent (clear its outbox first: `rm -rf agents/<key>/outbox/*`); **never hand-patch STATUS** (a missing STATUS usually means the subagent exited early and code w How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
task-swarm — standalone multi-agent orchestration (/task-swarm:swarm)
Host-tool convention 🔧: this skill orchestrates by dispatching subagents ("fork") and reading their completion status. Mechanism names — the
Task/Agenttool (dispatch a subagent), theExploreagent (a read-only investigation subagent), the subagent run-status display ("teammates UI", the ✓/streaming/running indicators) — are written for Claude-family hosts (Claude Code / CodeBuddy), where naming them directly is the most reliable. On a host that lacks a given mechanism, use its nearest equivalent (a subagent-dispatch tool / a read-only subagent / whatever surfaces subagent completion); with no subagent capability at all, run the groups sequentially as a single agent. On Codex specifically, subagent dispatch isspawn_agent/wait_agent/close_agentand requiresmulti_agent = truein~/.codex/config.toml(without it there is no dispatch tool → fall back to sequential single-agent);close_agenteach one when its work is done. Codex does not consume theagents/*.mdpersona files (they are Claude/CodeBuddy agent format), so on Codex the orchestrator passes each role's instructions inline and the per-role tool isolation (reviewer/validator having no Edit/Write) is not automatic — enforce it by prompt. A subagent counts as done only when the host confirms its dispatched task returned successfully — never from the subagent's own verbal report. The described behavior matters, not the exact tool name.
§0 Who you are
The lead agent = task-swarm's orchestrator + planner. task-swarm provides four things:
the pipeline.yml orchestration format, the state-machine CLI (task_swarm.py), the sub-agent role
definitions (coder/reviewer/validator), and report rendering.
The CLI only guards 4 points of mechanical integrity; all other orchestration judgment is yours, and the CLI does not constrain your thinking:
- schema validation (pipeline.yml format is legal)
- agent_key consistency (state machine and artifacts line up)
- advance artifact completeness / format checks
- atomic writes + blocking manual edits to controlled files
What ships with it
3 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.
- yesterday First seen · 136 lines · 74 tokens per session scan D 76dcae6dabc7
swarm is a skill published in the GitHub repository qxbyte/pluginhub (3 stars, last pushed 27d ago), licensed MIT. It adds 74 tokens to every session and 2,917 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it D with 2 findings (reads agent configuration directories, recursive force delete). 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.
Test Runner
Skill para ejecutar y gestionar tests. Incluye patrones de testing, fixtures comunes, y estrategias de debugging de tests fallidos.