Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/qxbyte/pluginhubnpx agentmods add skills/qxbyte/pluginhub/executeWrote 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/skills/qxbyte/pluginhub/execute)<a href="https://agentmods.dev/skills/qxbyte/pluginhub/execute"><img src="https://agentmods.dev/badge/skills/qxbyte/pluginhub/execute/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/skills/qxbyte/pluginhub/execute"><img src="https://agentmods.dev/badge/skills/qxbyte/pluginhub/execute.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.00086 | $0.02317 |
| Opus 5.5 | $0.00034 | $0.00927 |
| Sonnet 5.5 | $0.00017 | $0.00463 |
| Haiku 4.5 | $0.00009 | $0.00232 |
Grade A, and why
execute 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 1mo 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/specode:execute — run a spec's execution tail (selector → execution → acceptance)
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.
This skill owns everything from "tasks.md is ready" to "acceptance written": the 「执行方式」 selector, engine dispatch (including the task-swarm handoff), implementation-log.md appending, acceptance, and the distill prompt. It never generates requirements / design / tasks — earlier phases belong to the sibling spec / intake skills. Extracted from ../spec/SKILL.md as a pure relocation: the semantics below are unchanged from the pre-6.3.0 inline pipeline.
Entry contract (three callers, one behavior)
- Pipeline entry: Pipeline entry requires an explicitly approved
tasks.md; the orchestration must not invoke this skill from the same turn that created the plan. The spec orchestration shell (../spec/SKILL.mdFlow step 5) invokes this skill by name (specode:execute) via theSkilltool after that approval — slug and specsRoot are already in the conversation context; don't re-ask, but still run §Preflight to ground on on-disk state. - Manual entry: Manual entry is explicit approval of the existing
tasks.md, because the user directly requested/specode:execute <slug>. The user may do so at any time (typically after a session break, or after/specode:continue <slug>reported an executing/complete phase). slug is required — missing → report an error and suggest/specode:list. - continue handoff: when
/specode:continue <slug>infers phase ∈ {executing, complete, legacy 5.x} and the user gives the go-ahead, the continue skill invokes this skill via theSkilltool instead of re-deriving execution rules from prose.
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.
- 1mo ago First seen · 90 lines · 86 tokens per session scan A fe7b19de0403
execute is a skill published in the GitHub repository qxbyte/pluginhub (3 stars, last pushed 25d ago), licensed MIT. It adds 86 tokens to every session and 2,317 once invoked, about $0.0003 per session on Opus 5.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
shiny-py-optimize
Diagnose and fix performance problems in Shiny for Python apps — slow startup, sluggish interactions, blocking operations, and apps that struggle beyond a handful of concurrent users. Use when a Shiny for Python app is slow, hangs, recomputes too much, times out, or must support more users; when the user asks to…
sync-check
Walks the documentation dependency web after a CLI code change and reports which downstream files (skills, SOPs, READMEs, plugin references) are out of sync. Use after fixing a bug, adding a command, changing auth behavior, refactoring, or before committing — and when the user says "sync check", "update docs"…
gap-analyzer
Compares a CLI's implemented commands against its APP.md API map and traffic-analysis.json to find missing endpoints, incomplete CRUD, dead client methods, and priority gaps. Runs as the mandatory first step of /cli-anything-web:refine and as an optional pre-review scan in standards.
linkedin-cli
Interacts with LinkedIn via the cli-web-linkedin command-line tool — search people/jobs/companies, view profiles and feed, create/edit/delete posts, react and comment, manage connections and invitations, read and send messages, view notifications, follow companies. Use when the user asks about LinkedIn or wants to…
tripadvisor-cli
Searches TripAdvisor hotels, restaurants, attractions, and destinations via the cli-web-tripadvisor command-line tool, with detail lookups by URL. Use when the user asks about hotels, restaurants, things to do, travel destinations, or TripAdvisor ratings and reviews. Prefer this CLI over fetching the TripAdvisor…
youtube-cli
Searches YouTube and fetches video transcripts via the cli-web-youtube command-line tool — video search, video details (views, duration, description, keywords), trending by category, channel info, and timestamped transcripts/captions with language selection and translation. Use when the user asks about YouTube…