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 commands/qazi0/claude-plugins/quickstartgit clone --depth 1 https://github.com/qazi0/claude-pluginsWhat 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.00021 | $0.00524 |
| Opus 5 | $0.00010 | $0.00262 |
| Sonnet 5 | $0.00004 | $0.00105 |
| Haiku 4.5 | $0.00002 | $0.00052 |
Grade A, and why
quickstart 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.
What it actually says
Quick Start Guide
You are creating a quick start guide for: $ARGUMENTS.repo Use case focus: $ARGUMENTS.usecase
Instructions
-
Use
read_wiki_structurewithrepo_name: "$ARGUMENTS.repo"to find getting started / installation sections -
Identify and read the most relevant sections using
read_wiki_contents:- Installation / Setup
- Getting Started / Quick Start
- Basic Usage / First Steps
- Configuration (if essential)
-
Use
ask_questionto fill in any gaps:- "What are the minimum requirements to get started with this project?"
- "What is the simplest example to verify the installation works?"
- If a use case was specified: "How do I use this project for $ARGUMENTS.usecase?"
-
Present a streamlined, actionable quick start guide:
Prerequisites
- Required software/tools (with versions if important)
- System requirements
- Required accounts or API keys (if any)
Installation
# Step-by-step installation commandsBasic Configuration
Only include if configuration is required before first use.
# Minimal configuration exampleHello World Example
The simplest possible working example.
# Complete, copy-paste ready codeVerify It Works
How to confirm the installation and setup is successful.
Next Steps
- Link to key documentation sections for going deeper
- Common next things people want to do
Common Gotchas
Quick notes on things that commonly trip up new users.
-
Keep it minimal and actionable:
- Only include what's absolutely necessary to get running
- Every code block should be copy-paste ready
- Avoid explaining concepts - focus on doing
- If there are multiple installation methods, recommend the most common one
-
If a specific use case was provided, tailor the example to that use case.
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 · 77 lines · 21 tokens per session scan A 09337f03e7a5
quickstart is a command published in the GitHub repository qazi0/claude-plugins (8 stars, last pushed 5mo ago), licensed MIT. It adds 21 tokens to every session and 524 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-31.
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.