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 skills add acostanzo/quickstop --skill honegit clone --depth 1 https://github.com/acostanzo/quickstopWrote 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/acostanzo/quickstop/hone)<a href="https://agentmods.dev/skills/acostanzo/quickstop/hone"><img src="https://agentmods.dev/badge/skills/acostanzo/quickstop/hone/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/acostanzo/quickstop/hone"><img src="https://agentmods.dev/badge/skills/acostanzo/quickstop/hone.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.00017 | $0.03091 |
| Opus 5.5 | $0.00007 | $0.01236 |
| Sonnet 5.5 | $0.00003 | $0.00618 |
| Haiku 4.5 | $0.00002 | $0.00309 |
Grade A, and why
hone 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 — 344 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hone: Plugin Quality Auditor
You are the Hone orchestrator. When the user runs /hone <plugin-name>, execute this 5-phase audit workflow. Follow each phase in order. Do not skip phases.
Phase 0: Discovery
Step 1: Parse Plugin Name
Extract the plugin name from $ARGUMENTS. If empty or missing, list available plugins by globbing plugins/*/ and use AskUserQuestion to ask which to audit.
Step 2: Validate Plugin Exists
Glob for plugins/$ARGUMENTS/.claude-plugin/plugin.json. If not found, tell the user the plugin doesn't exist and abort.
Step 3: Build Plugin Manifest
Run parallel Glob calls to discover all files under plugins/<name>/:
| Category | Glob Pattern |
|---|---|
| Metadata | plugins/<name>/.claude-plugin/*.json |
| Skills | plugins/<name>/skills/*/SKILL.md |
| Skill references | plugins/<name>/skills/*/references/*.md |
| Agents | plugins/<name>/agents/*.md |
| Hooks | plugins/<name>/hooks/*.json |
| MCP | plugins/<name>/.mcp.json |
| Docs | plugins/<name>/README.md |
| Legacy | plugins/<name>/commands/*.md |
| All files | plugins/<name>/**/* |
Get line counts for all discovered files via a single Bash call: wc -l <file1> <file2> ...
Step 4: Present Plugin Map
=== PLUGIN MAP ===
Plugin: <name> v<version>
Skills (N):
skills/<skill>/SKILL.md XX lines
skills/<skill>/references/foo.md XX lines
Agents (N):
agents/<agent>.md XX lines
Hooks:
hooks/hooks.json XX lines
Metadata:
.claude-plugin/plugin.json XX lines
README.md XX lines
Legacy:
[commands/ if found]
Total: N files, ~N lines
=== END MAP ===
Tell the user:
Phase 1: Building expert context from official plugin documentation...
Phase 1: Build Expert Context
Step 1: Load Expert Context
Invoke /claudit:knowledge ecosystem to retrieve ecosystem knowledge.
If the skill runs successfully (outputs === CLAUDIT KNOWLEDGE: ecosystem === block):
- Use its output as the ecosystem portion of Expert Context
- Also read
.claude/skills/smith/references/plugin-spec.mdfor plugin-authoring-specific detail (plugin.json schema, directory conventions) that the ecosystem cache may not cover at full depth - Combine both as Expert Context
- Skip to Phase 2
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 · 344 lines · 17 tokens per session scan A 5ab90a2101ea
hone is a skill published in the GitHub repository acostanzo/quickstop (46 stars, last pushed 4mo ago), licensed MIT. It adds 17 tokens to every session and 3,091 once invoked, about $0.0001 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-30.
Other skills, from other repositories
create-pull-request
Use when asked to create or update a PR, revise its description, or link issue references to its body. Not for multi-PR stacks: use gate-and-merge. Not for releases: use git-workflow-and-versioning.
audit-project
Run an iterative multi-agent code audit until critical and high findings are resolved. Use when the user says "audit my code", "find all the bugs", "deep code audit", "iterative review", or "review until clean".
gate-and-merge
Use when landing a queue of open PRs: gate each PR, sweep its review feedback to root cause, then merge, repair, hold, or close it. Human-only.
doubt-driven
Use when a non-trivial decision sits under uncertainty and correctness matters more than speed. Not for patch review: use review. Not for plan attacks: use load-bearing-assumption-test.
pr-review-canvas-html
Use when asked to render a GitHub PR as a standalone review HTML page. Fetches PR data via gh API, renders diffs with move detection, and serves the artifact on a local port. Not for Cursor Canvas output — use pr-review-canvas.
code-quality
QUANTITATIVE structural metrics on TS/Python -- function length, cyclomatic complexity, nesting, duplication, code smells -- scored report. NOT for conventions/any checks (use code-standards) or API alignment (use api-contract).