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/continueWrote 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/continue)<a href="https://agentmods.dev/skills/qxbyte/pluginhub/continue"><img src="https://agentmods.dev/badge/skills/qxbyte/pluginhub/continue/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/continue"><img src="https://agentmods.dev/badge/skills/qxbyte/pluginhub/continue.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.00060 | $0.01448 |
| Opus 5.5 | $0.00024 | $0.00579 |
| Sonnet 5.5 | $0.00012 | $0.00290 |
| Haiku 4.5 | $0.00006 | $0.00145 |
Grade A, and why
continue 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/specode:continue — resume an existing spec
Host-tool convention 🔧: tool names in this skill — the
Skilltool (invoke another skill by name),AskUserQuestion(structured multiple-choice question) — 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 skill-invocation mechanism / a structured-question tool); with no equivalent, fall back to reading the target skill'sSKILL.mddirectly / plain-text prose. The described behavior is what matters, not the exact tool name.
/specode:continue <slug> loads an existing spec's context and reports where it stands, then stops. It never auto-resumes. This skill owns only the load-and-stop entry + phase inference; the actual pipeline lives in the sibling ../spec/SKILL.md.
Resolver
specode CLIs go through the run.sh wrapper in the plugin's scripts/ directory — relative to this skill that is ../../scripts/; use this skill's base directory to turn the relative path into an absolute one (do not resolve env vars, do not find the cache):
sh ../../scripts/run.sh ../../scripts/resolve_root.py get-root
Flow
- slug is required; if missing → report an error and suggest
/specode:listto find slugs. resolve_root.py get-root(exit 3 not configured → first-time setup; exit 4 configured but unreachable — external drive not mounted / path gone → surface the cause and re-prompt for a path rather than reporting "slug not found"; both per../spec/SKILL.md§specsRoot resolution) → on exit 0, locate<specsRoot>/<slug>/; directory not found → report an error and suggest/specode:list.- Read every fixed doc present, infer the phase per the table below, then report a progress brief and stop — do not auto-resume.
Load-and-stop 🔒: /specode:continue <slug> never auto-resumes. It does exactly three things: (1) locate <specsRoot>/<slug>/ and read every fixed doc present; (2) report a progress brief — slug, inferred phase, per-doc existence, tasks.md checkbox progress (x/N; legacy specs: design.md checkboxes), and what the next action would be; (3) stop and wait for the user's instruction. Only when the user says 继续 (or equivalent) does execution resume from the inferred phase; if the user instead supplies requirement changes, digest them into the affected docs first, then ask whether to resume. The "Resume action" column below describes what happens after the user gives the go-ahead — it is not automatic behavior.
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 · 55 lines · 60 tokens per session scan A f388d85cca06
continue is a skill published in the GitHub repository qxbyte/pluginhub (3 stars, last pushed 25d ago), licensed MIT. It adds 60 tokens to every session and 1,448 once invoked, about $0.0002 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
learn
Use when users /learn, save, remember, or distill lessons.
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…