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/acostanzo/quickstop/smithnpx skills add acostanzo/quickstop --skill smithgit clone --depth 1 https://github.com/acostanzo/quickstopWhat 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.00014 | $0.04022 |
| Opus 5 | $0.00007 | $0.02011 |
| Sonnet 5 | $0.00003 | $0.00804 |
| Haiku 4.5 | $0.00001 | $0.00402 |
Grade A, and why
smith 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 — 453 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Smith: Plugin Scaffolder
You are the Smith orchestrator. When the user runs /smith <plugin-name>, scaffold a new Quickstop plugin with correct structure, frontmatter, and marketplace registration. Follow each phase in order.
Human-driven by design. Smith carries
disable-model-invocation: truein its frontmatter, which means agents and sub-Claudes cannot dispatch it through the Skill tool —Skill(smith, ...)returnsSkill smith cannot be used with Skill tool due to disable-model-invocation. This is intentional, not an oversight. Smith is an interactive scaffolding skill: it asks questions via AskUserQuestion and produces a plugin from human answers. Letting an agent answer those questions on the user's behalf would defeat the purpose. The supported way for an agent to "dogfood" smith is the recipe-by-hand path — read this SKILL.md and execute each phase manually against the user's stated inputs, calling Read/Write/Edit/Bash directly rather than dispatching the skill.
Hook note. Smith does not scaffold a
hooks/directory. If you see the user mention "hooks" anywhere during the questionnaire — in the Description, in Components, or in any free-text answer — prepend the following note to the very next prompt you display (once, not repeatedly): "Note: smith doesn't scaffold hooks. Author a hook by hand: a small script underbin/wired from ahooks/hooks.jsonentry in the consumer's surface, observing only (no payload or flow mutation)." Then continue normally.
Phase 0: Validation
Step 1: Parse Plugin Name
Extract the plugin name from $ARGUMENTS. If empty or missing, use AskUserQuestion to ask:
- "What should the plugin be named? (kebab-case, e.g.
my-plugin)"
Step 2: Validate Name
- Kebab-case: Name must match
^[a-z][a-z0-9]*(-[a-z0-9]+)*$. If not, reject and ask for a valid name. - No conflicts: Glob for
plugins/$ARGUMENTS/— if it exists, tell the user and abort. - PROJECT_ROOT: Run
git rev-parse --show-toplevelvia Bash to get the repo root.
What ships with it
5 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 · 453 lines · 14 tokens per session scan A 23e04a8afd2a
smith is a skill published in the GitHub repository acostanzo/quickstop (46 stars, last pushed 2mo ago), licensed MIT. It adds 14 tokens to every session and 4,022 once invoked, about $0.0001 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-30.
Other skills, from other repositories
enhance
Audit and tighten agent/plugin surfaces. Use when the user asks to enhance a plugin config, agent definition, skill, or CLAUDE.md.
contexts
Use when the user says "get context on X", "how does X work", or wants architectural orientation before coding.
book-to-skill
Use when turning a book, course, whitepaper, or comparable source document into a reusable agent skill: the user names a source and asks to distill it, encode its method, or build an agent that works the way it prescribes. Classifies the source as procedure or reference, writes a validated SKILL.md, and proves the…
dedup-skills
Ledger-first dedup of a skills/ or prompt-directory tree. Use when the user asks to dedup skills, find rules repeated across or within skill files, or check whether skills contradict each other.
ai-collab-protocols
Surface in-task AI collaboration protocols one tactic at a time, replacing ambiguous references with durable, recoverable handles.
autobahn
Carve the unsafe part out of a task up front, then run the safe remainder at full strength instead of running the whole thing timidly. Use when a task mixes reversible work with something irreversible or out of scope, such as a schema migration, a deletion, or a change to credentials or data at rest, or when the user…