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.
git clone --depth 1 https://github.com/davistroy/claude-marketplaceWrote 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/commands/davistroy/claude-marketplace/scaffold-plugin)<a href="https://agentmods.dev/commands/davistroy/claude-marketplace/scaffold-plugin"><img src="https://agentmods.dev/badge/commands/davistroy/claude-marketplace/scaffold-plugin/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/commands/davistroy/claude-marketplace/scaffold-plugin"><img src="https://agentmods.dev/badge/commands/davistroy/claude-marketplace/scaffold-plugin.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.00014 | $0.03027 |
| Opus 5 | $0.00007 | $0.01514 |
| Sonnet 5 | $0.00003 | $0.00605 |
| Haiku 4.5 | $0.00001 | $0.00303 |
Grade A, and why
scaffold-plugin 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 5d 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 — 397 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scaffold Plugin
Create a new Claude Code plugin with the proper directory structure, configuration files, and starter templates. This command ensures new plugins follow the established conventions.
Input Validation
Optional Arguments:
<plugin-name>- Name for the new plugin (kebab-case ending in-plugin)--dry-run- Show the directory structure and file list that would be created without creating any files--with-commands- Also scaffold acommands/directory (legacy format — see ADR-0006). Default scaffold is skills-only.
Validation: If arguments are missing, the command will prompt interactively.
Plugin name must be:
- kebab-case format ending in
-plugin(e.g.,my-new-plugin) - Unique (not already exist in
plugins/directory) - Descriptive but concise
- Contain only lowercase letters, numbers, and hyphens (no special characters, no spaces)
Instructions
Phase 1: Gather Information
Interactively collect the following from the user:
1.1 Plugin Name
Ask:
What is the plugin name? (kebab-case ending in '-plugin', e.g., "data-tools-plugin")
Validate:
- Must be kebab-case: lowercase letters, numbers, hyphens only
- Must end with
-plugin - Must not contain special characters (underscores, dots, spaces)
- Must not already exist in
plugins/directory (scan with Glob)
If invalid:
Error: Plugin name must be kebab-case ending in '-plugin'
Invalid: [what was provided]
Reason: [specific reason]
Please provide a valid plugin name:
1.2 Description
Ask:
Provide a brief description for the plugin:
Validate:
- Must be non-empty
- Should describe the plugin's purpose
1.3 Category
Ask:
Select a category for the plugin:
[1] productivity - Personal productivity and workflow tools
[2] workflow - Process automation and management
[3] analysis - Code and data analysis tools
[4] integration - External service integrations
[5] utility - General utility commands
[6] custom - Enter a custom category
Enter number (1-6) or category name:
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.
- 5d ago First seen · 397 lines · 14 tokens per session scan A 13c8347acc1e
scaffold-plugin is a command published in the GitHub repository davistroy/claude-marketplace (5 stars, last pushed yesterday), licensed MIT. It adds 14 tokens to every session and 3,027 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-09-04.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.