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/juanmhidalgo/claude-pluginsWrote 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/juanmhidalgo/claude-plugins/start)<a href="https://agentmods.dev/commands/juanmhidalgo/claude-plugins/start"><img src="https://agentmods.dev/badge/commands/juanmhidalgo/claude-plugins/start/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/juanmhidalgo/claude-plugins/start"><img src="https://agentmods.dev/badge/commands/juanmhidalgo/claude-plugins/start.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.00037 | $0.00699 |
| Opus 5.5 | $0.00015 | $0.00280 |
| Sonnet 5.5 | $0.00007 | $0.00140 |
| Haiku 4.5 | $0.00004 | $0.00070 |
Grade A, and why
start 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 23d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Onboarding
Generate a comprehensive onboarding guide for this project.
Focus area (optional): $ARGUMENTS
Phase 1: Project Discovery
- Project Type - What kind of project is this? (web app, API, CLI, library)
- Tech Stack - Languages, frameworks, major dependencies
- Entry Points - Main files, how the app starts
- Project Structure - Directory layout and organization pattern
- Configuration - Key config files, environment setup
- Documentation - README, CLAUDE.md, docs folder
If a focus area was provided, prioritize that domain.
Phase 2: Generate Onboarding Guide
<output_format> Produce a structured guide:
# [Project Name] Onboarding Guide
## Quick Start
- How to install dependencies
- How to run the project
- How to run tests
## Architecture Overview
- High-level description (2-3 sentences)
- Key directories and their purpose
- Data flow (how requests/data move through the system)
## Tech Stack
| Layer | Technology | Purpose |
|-------|------------|---------|
| Frontend | ... | ... |
| Backend | ... | ... |
| Database | ... | ... |
## Key Files to Read First
1. `path/to/file` - Why it's important
2. `path/to/file` - Why it's important
3. `path/to/file` - Why it's important
## Common Patterns
- [Pattern 1]: How it's used, example file
- [Pattern 2]: How it's used, example file
## Development Workflow
- How to create a feature branch
- How to run linters/formatters
- How to submit a PR
## Gotchas & Tribal Knowledge
- Things that aren't obvious from the code
- Common mistakes new developers make
- Quirks specific to this project
## Next Steps
- Suggested first task for a new developer
- Areas to explore based on your role
</output_format>
<critical_rules> Base every section on what onboard-discoverer found or on files you read; mark anything unverified.
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.
- 23d ago Changed 92100915eb05
- 1mo ago First seen · 109 lines · 37 tokens per session scan A 6f4693929958
start is a command published in the GitHub repository juanmhidalgo/claude-plugins (8 stars, last pushed 2d ago), licensed MIT. It adds 37 tokens to every session and 699 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-09-03.
Other commands, from other repositories
learn-story-flow
Learn story-flow concepts with interactive guidance for junior developers.
start-10-1
A guided lesson on setting up clasp, a command-line tool for managing Google Apps Script projects, and connecting it to Google’s Apps Script API.
start-0-8
A Japanese-language command that displays the current project setup progress.
setup-m365cli.es
Lesson command — Setup de M365 CLI.
prep-role
Deep prep for a specific role's interview process. The user wants to know what to expect, how to win, and what kills candidates at their level.
setup-vercel.es
Command "setup-vercel.es" from minicoohei/ai-agent-camp, covering configuración de vercel cli, step 0: verificar progreso de configuración, lo que hará en esta sesión, verificación de preparación and step 1: crear cuenta de vercel.