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 skills/legacybridge-tech/claude-plugins/initialize-projectnpx skills add legacybridge-tech/claude-plugins --skill initialize-projectgit clone --depth 1 https://github.com/legacybridge-tech/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.00064 | $0.06305 |
| Opus 5 | $0.00032 | $0.03152 |
| Sonnet 5 | $0.00013 | $0.01261 |
| Haiku 4.5 | $0.00006 | $0.00630 |
Grade A, and why
initialize-project 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.
How it starts
The opening of the file, as written. The whole thing — 987 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Initialize Project Skill
When to use this Skill
Activate when the user:
- Mentions starting or creating a new project
- Uses keywords: "new project", "start project", "initialize project", "create project", "set up project"
- Wants to set up project management structure
- Needs to configure project documentation
Workflow
Phase 1: Project Identification
Objective: Understand what project we're setting up.
Steps:
- Extract project name from user message if provided
- Determine target directory:
- If in a directory already, offer to initialize there
- If project name given, create new directory
- Otherwise, ask where to create the project
- Check for existing structure:
- Use
lsto check if directory exists - Use
Readto check for existing RULE.md - Warn if project already initialized
- Use
Example:
User: "I want to create a new project called Mobile App Redesign"
Detected:
- Project name: "mobile-app-redesign" (slugified)
- Action: Create new directory
Phase 2: Interactive Q&A
Objective: Gather complete information about team workflow and preferences.
Use AskUserQuestion tool with clear, focused questions. Each question should offer specific options.
Question Set 1: Development Methodology
Question: "What development methodology does your team use?"
Options to present:
- Scrum - Time-boxed sprints with ceremonies (planning, daily standup, review, retrospective)
- Kanban - Continuous flow with WIP limits and visual board
- Waterfall - Sequential phases with formal handoffs
- Agile (general) - Iterative development without strict Scrum ceremonies
- Hybrid/Custom - Combination of methodologies
Follow-up questions based on choice:
If Scrum selected:
- "How long are your sprints?" (1 week / 2 weeks / 3 weeks / 4 weeks)
- "Do you hold daily standups?" (Yes / No)
- "Sprint ceremonies to track?" (Planning, Review, Retrospective - multiSelect)
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 · 987 lines · 64 tokens per session scan A 747247d90ed2
initialize-project is a skill published in the GitHub repository legacybridge-tech/claude-plugins (6 stars, last pushed 3mo ago), licensed MIT. It adds 64 tokens to every session and 6,305 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.