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/lucasnad27/claude-plugins/guidenpx skills add lucasnad27/claude-plugins --skill guidegit clone --depth 1 https://github.com/lucasnad27/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/skills/lucasnad27/claude-plugins/guide)<a href="https://agentmods.dev/skills/lucasnad27/claude-plugins/guide"><img src="https://agentmods.dev/badge/skills/lucasnad27/claude-plugins/guide.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 | $0.00019 | $0.00723 |
| Opus 5 | $0.00010 | $0.00362 |
| Sonnet 5 | $0.00004 | $0.00145 |
| Haiku 4.5 | $0.00002 | $0.00072 |
Grade A, and why
guide 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 4d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Guide
You provide contextual orientation for the research-design-plan-implement workflow.
Two modes:
/guide(no args) → Short orientation: where am I, what's next? (5-10 lines max)/guide [topic]→ Deep dive on a specific topic (seetopics.mdin this skill's directory)
Mode 1: Orientation (no args)
Current Workspace State
Recent research docs:
!ls -lt .rpi/*-research.md 2>/dev/null | head -3
Recent design docs:
!ls -lt .rpi/*-design.md 2>/dev/null | head -3
Recent plan docs:
!ls -lt .rpi/*-plan.md 2>/dev/null | head -3
Git status:
!git status --short 2>/dev/null
PR status:
!gh pr status 2>/dev/null | head -5
Determine Current Phase
Based on the workspace state above:
- No artifacts → Getting started
- Research doc exists, no design → Ready for design
- Design doc exists, no plan → Ready for planning
- Plan doc exists, some phases incomplete → In implementation
- Plan doc with all phases complete → Ready for review
- Open PR → In review
Output Format
Respond with ONLY this format:
**[Current phase]**
[Most relevant artifact with path]
Next: [What to do next with the specific command]
Tip: [One-line tip relevant to current phase]
Phase-Specific Tips
- Getting started: "Start with /research-codebase to explore the area you'll be working in."
- Ready for design: "This is your highest-leverage review moment — corrections here save hundreds of lines of rework."
- Ready for planning: "/create-plan takes your design and produces vertical phases with per-phase testing."
- In implementation: "Each phase should be testable on its own. If it's not, the plan may need vertical restructuring."
- Ready for review: "Run /prepare-pr to commit, open the PR, and land a numbered review guide — a short index in the description, the detail as inline comments on the diff."
- In review: "Each stop is a resolvable thread; resolving one ticks it off. Point /prepare-pr at an existing PR number to write a guide onto a PR opened outside the loop."
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 82 lines · 19 tokens per session scan A 26b31b6dd605
guide is a skill published in the GitHub repository lucasnad27/claude-plugins (3 stars, last pushed 6d ago), licensed MIT. It adds 19 tokens to every session and 723 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 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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…