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/byeongminlee/nextjs-claude-code/claude-plugin-referencenpx skills add ByeongminLee/nextjs-claude-code --skill claude-plugin-referencegit clone --depth 1 https://github.com/ByeongminLee/nextjs-claude-codeWhat 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.00127 | $0.00718 |
| Opus 5 | $0.00063 | $0.00359 |
| Sonnet 5 | $0.00025 | $0.00144 |
| Haiku 4.5 | $0.00013 | $0.00072 |
Grade A, and why
claude-plugin-reference 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Plugin Reference
A curated analysis of major Claude Code plugins and spec-driven development tools. Each reference file covers architecture, key features, pros/cons, and unique approaches.
Plugin Reference Table
| Plugin | Focus | Reference File | When to Read |
|---|---|---|---|
| Get Shit Done (GSD) | Spec-driven workflow with multi-agent orchestration | references/get-shit-done.md |
Full project lifecycle, wave execution, context engineering, XML prompts |
| gstack | Virtual engineering team with sprint workflow | references/gstack.md |
Role-based skills, browser testing, deployment pipelines, parallel sprints |
| Everything Claude Code (ECC) | Performance optimization system | references/everything-claude-code.md |
Token optimization, 116 skills, continuous learning, AgentShield security |
| Oh My OpenAgent (OmO) | Multi-model orchestration | references/oh-my-openagent.md |
Multi-provider agents, hash-anchored edits, LSP/AST integration |
| Superpowers | TDD-focused development workflow | references/superpowers.md |
Test-driven development, systematic debugging, subagent-driven dev |
| Vercel Plugin | Vercel ecosystem expertise | references/vercel-plugin.md |
Vercel deployment, Next.js, AI SDK, 47 specialized skills |
| Spec Kit | Spec-driven development framework | references/spec-kit.md |
SDD methodology, constitution, specification, 30+ AI agent support |
| OpenSpec | Lightweight spec framework | references/openspec.md |
Proposal-driven workflow, artifact management, lightweight SDD |
Read only the relevant reference file(s). Do NOT load all at once.
Quick Comparison by Category
Spec-Driven Development (SDD)
When the user asks about SDD, specifications, or structured development planning, read Spec Kit and OpenSpec first. GSD also has strong spec-driven elements.
Full Lifecycle Workflow
For end-to-end project management (plan → build → test → ship): GSD, gstack, Superpowers
What ships with it
8 files 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.
- 2d ago First seen · 44 lines · 127 tokens per session scan A 10e16ba965ee
claude-plugin-reference is a skill published in the GitHub repository ByeongminLee/nextjs-claude-code (3 stars, last pushed 5mo ago), licensed MIT. It adds 127 tokens to every session and 718 once invoked, about $0.0006 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
server-setup
Initialize tRPC with initTRPC.create(), define routers with t.router(), create procedures with .query()/.mutation()/.subscription(), configure context with createContext(), export AppRouter type, merge routers with t.mergeRouters(), lazy-load routers with lazy().
client-setup
Create a vanilla tRPC client with createTRPCClient (), configure link chain with httpBatchLink/httpLink, dynamic headers for auth, transformer on links (not client constructor). Infer types with inferRouterInputs and inferRouterOutputs. AbortController signal support. TRPCClientError typing.
non-json-content-types
Handle FormData, file uploads, Blob, Uint8Array, and ReadableStream inputs in tRPC mutations. Use octetInputParser from @trpc/server/http for binary data. Route non-JSON requests with splitLink and isNonJsonSerializable() from @trpc/client. FormData and binary inputs only work with mutations (POST).
caching
Set HTTP cache headers on tRPC query responses via responseMeta callback for CDN and browser caching. Configure Cache-Control, s-maxage, stale-while-revalidate. Handle caching with batching and authenticated requests. Avoid caching mutations, errors, and authenticated responses.
saas-builder
Clone, verify, map, and build on top of ixartz/SaaS-Boilerplate for a user's SaaS idea. Use when a user wants to reuse SaaS Boilerplate, evaluate how their product fits it, or build product-specific pages, database schema, roles, permissions, MVP features, and launch scope on top of the boilerplate.
trigger-authoring-tasks
Covers writing backend Trigger.dev tasks with @trigger.dev/sdk: defining task() and schemaTask(), the run function and its ctx, retries, waits, queues and concurrency, idempotency keys, run metadata, logging, triggering other tasks (and the Result shape), scheduled/cron tasks, and the essentials of trigger.config.ts.…