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/cicababba/claude-plugins-marketplace/initgit clone --depth 1 https://github.com/cicababba/claude-plugins-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/cicababba/claude-plugins-marketplace/init)<a href="https://agentmods.dev/commands/cicababba/claude-plugins-marketplace/init"><img src="https://agentmods.dev/badge/commands/cicababba/claude-plugins-marketplace/init.svg" alt="Measured on agentmods" 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.00000 | $0.00913 |
| Opus 5 | $0.00000 | $0.00456 |
| Sonnet 5 | $0.00000 | $0.00183 |
| Haiku 4.5 | $0.00000 | $0.00091 |
Grade A, and why
init 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/init — Initialize Development Session
Initialize a structured development session for any development task (new feature, bug fix, refactoring, performance optimization, etc.).
ABSOLUTE SCOPE & RESTRICTIONS
- This command ONLY initializes a development session.
- It MUST ONLY:
- gather context,
- gather specifications via Q&A,
- generate the
context-analysis.mdandspecification.mdfiles, - update
.claude/dev-sessions/.current-session.
- It MUST NEVER:
- perform any planning,
- generate a development plan,
- create any section or content titled "Plan", "Planning", "Implementation Plan", "Roadmap", or similar.
- Planning is done ONLY by the separate
development-planneragent viadev-plan-orchestratorskill, AFTER this command has completed. - IMPORTANT: This command must never produce code snippets or implementations, only analysis and specifications.
- IMPORTANT: All generated files (context-analysis.md, specification.md) must ALWAYS be written in ENGLISH, regardless of the language used in the conversation.
1. Create Session
Skill: Use
session-managerto create a new session
- Ask user for task description
- Generate session slug from description
- Create session directory:
.claude/dev-sessions/YYYY-MM-DD-HHMM-${slug}/ - Initialize
session.mdwith Session Overview (Status: PLANNING) - Update
.claude/dev-sessions/.current-sessionwith session path
2. Context Analysis
Skill: Use
dev-context-analysisto analyze relevant code paths
- Ask the user which files or folders to analyze for context
- Give examples (e.g.,
/src/auth,/src/models/user.ts) - When user provides paths, invoke
dev-context-analysisskill with:- Session path
- List of paths to analyze
- The skill will:
- Analyze each path for patterns, dependencies, tests, implementation details
- Generate structured
context-analysis.md - Save via
artifact-fs-manager
- Present a Quick Summary to the user
IMPORTANT: In this step you are ONLY analyzing. Do NOT start planning, do NOT propose implementation steps.
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 · 113 lines · 0 tokens per session scan A 699d605a1cba
init is a command published in the GitHub repository cicababba/claude-plugins-marketplace (3 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 913 tokens. 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.