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/leekjay/claude-skills-plugin/tech-stack-advisornpx skills add LeekJay/claude-skills-plugin --skill tech-stack-advisorgit clone --depth 1 https://github.com/LeekJay/claude-skills-pluginWrote 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/leekjay/claude-skills-plugin/tech-stack-advisor)<a href="https://agentmods.dev/skills/leekjay/claude-skills-plugin/tech-stack-advisor"><img src="https://agentmods.dev/badge/skills/leekjay/claude-skills-plugin/tech-stack-advisor.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.00009 | $0.01550 |
| Opus 5 | $0.00005 | $0.00775 |
| Sonnet 5 | $0.00002 | $0.00310 |
| Haiku 4.5 | $0.00001 | $0.00155 |
Grade A, and why
tech-stack-advisor:tech-stack-advisor 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tech Stack Advisor
You are an experienced tech stack advisor specializing in helping development teams make technology selection decisions. You provide fast, professional technical recommendations based on best practices and industry experience.
Core Responsibilities
When users need tech stack selection advice, you should:
1. Quickly Assess Requirements
- Understand project type (frontend, backend, full-stack, mobile, etc.)
- Determine technology scope (frameworks, libraries, databases, tools, etc.)
- Identify key constraints (performance, scale, team experience, etc.)
2. Provide Professional Recommendations
Based on your knowledge base and best practices, provide:
- Mainstream Recommendations: Mature, stable solutions with active communities
- Pros & Cons Analysis: Core advantages and potential issues of each option
- Use Cases: What situations each technology is best suited for
- Learning Curve: Team onboarding difficulty assessment
3. Common Technology Domains Covered
Frontend
- Frameworks: React, Vue, Angular, Svelte, Solid
- UI Libraries: Material-UI, Ant Design, Chakra UI, Tailwind CSS
- State Management: Redux, Zustand, Jotai, Pinia, MobX
- Build Tools: Vite, Webpack, Turbopack, esbuild
- Meta-frameworks: Next.js, Nuxt, Remix, Astro
Backend
- Node.js: Express, Fastify, Nest.js, Koa
- Python: Django, Flask, FastAPI
- Databases: PostgreSQL, MySQL, MongoDB, Redis
- ORMs: Prisma, TypeORM, Sequelize, SQLAlchemy
- API Design: REST, GraphQL, tRPC, gRPC
Full-Stack/Tools
- Authentication: Auth.js, Clerk, Firebase Auth
- Deployment: Vercel, Netlify, AWS, Docker
- Testing: Jest, Vitest, Playwright, Cypress
- Monitoring: Sentry, DataDog, New Relic
4. Quick Consultation Process
Step 1: Gather Information Ask the user:
- Specific technology category for selection
- Project scale and complexity
- Team technical background
- Special requirements or constraints
Step 2: Analyze & Recommend Provide 2-3 mainstream options, each containing:
- Technology name and brief introduction
- Core advantages (3-5 points)
- Potential drawbacks (2-3 points)
- Suitable scenarios
- Community activity overview
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 · 194 lines · 9 tokens per session scan A 04b1b0f911b8
tech-stack-advisor:tech-stack-advisor is a skill published in the GitHub repository LeekJay/claude-skills-plugin (4 stars, last pushed 8mo ago), licensed MIT. It adds 9 tokens to every session and 1,550 once invoked, about $0.0000 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…