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/rungchan2/frontend-skills/tech-stacknpx skills add rungchan2/frontend-skills --skill tech-stackgit clone --depth 1 https://github.com/rungchan2/frontend-skillsWrote 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/rungchan2/frontend-skills/tech-stack)<a href="https://agentmods.dev/skills/rungchan2/frontend-skills/tech-stack"><img src="https://agentmods.dev/badge/skills/rungchan2/frontend-skills/tech-stack.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.00072 | $0.01387 |
| Opus 5 | $0.00036 | $0.00694 |
| Sonnet 5 | $0.00014 | $0.00277 |
| Haiku 4.5 | $0.00007 | $0.00139 |
Grade A, and why
tech-stack scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s https://registry.npmjs.org/PACKAGE_NAME/latest | jq '.version' 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 Generator
프로젝트의 기술 스택과 의존성을 정의하는 문서 생성 가이드.
워크플로우
1. 인터뷰 → 2. 패키지 버전 조회 → 3. 문서 생성 → 4. 검토/보완
패키지 버전 조회
중요: 패키지 버전 명시 시 반드시 최신 버전을 조회하여 기입한다.
스크립트 사용
# 특정 패키지 조회
python scripts/get_npm_versions.py react next typescript axios
# 카테고리별 조회
python scripts/get_npm_versions.py --category frontend
python scripts/get_npm_versions.py --category styling
python scripts/get_npm_versions.py --category state
# 마크다운 형식 출력 (문서에 바로 복사 가능)
python scripts/get_npm_versions.py react next --format markdown
# 전체 카테고리 조회
python scripts/get_npm_versions.py --all
# 카테고리 목록 확인
python scripts/get_npm_versions.py --list
카테고리 목록
frontend: react, next, vue, nuxt, svelte, typescript, vitestyling: tailwindcss, postcss, sass, emotion, styled-componentsui: radix-ui, headlessui, mui, chakra-ui, antdstate: zustand, jotai, redux, tanstack-query, swrforms: react-hook-form, zod, yupbackend: express, fastify, hono, nestjs, prisma, drizzle-orm, trpctesting: vitest, jest, testing-library, playwright, cypressutils: axios, date-fns, dayjs, lodash, clsxicons: lucide-react, heroicons, phosphor-icons
수동 조회 (스크립트 없이)
curl -s https://registry.npmjs.org/PACKAGE_NAME/latest | jq '.version'
인터뷰 질문
순차적으로 질문하여 정보 수집. 한 번에 2-3개씩 질문.
필수 질문
기존 환경
- "기존에 사용 중인 기술이 있나요?"
- "팀의 기술 스택 선호도는?"
규모 및 요구사항
- "예상 트래픽/사용자 수는?"
- "연동해야 하는 외부 서비스는?"
인프라
- "클라우드 선호도는? (AWS/GCP/Vercel 등)"
- "CI/CD 요구사항은?"
선택 질문 (필요시)
- "모노레포 구성이 필요한가요?"
- "테스트 커버리지 요구사항은?"
- "모니터링/로깅 요구사항은?"
Tech Stack 템플릿
# Tech Stack: [서비스명]
## 1. 프론트엔드
### 코어
| 항목 | 선택 | 버전 | 선택 이유 |
|------|------|------|----------|
| 프레임워크 | | | |
| 언어 | | | |
| 스타일링 | | | |
| UI 라이브러리 | | | |
### 상태관리
- **클라이언트**:
- **서버 상태**:
### 주요 패키지
| 패키지명 | 버전 | 용도 |
|---------|------|------|
| | | |
## 2. 백엔드
### 코어
| 항목 | 선택 | 버전 | 선택 이유 |
|------|------|------|----------|
| 프레임워크 | | | |
| 언어 | | | |
| 아키텍처 | | | |
| API 스타일 | | | |
### 주요 패키지
| 패키지명 | 버전 | 용도 |
|---------|------|------|
| | | |
## 3. 데이터베이스
| 용도 | 선택 | 호스팅 | 선택 이유 |
|------|------|--------|----------|
| Primary DB | | | |
| 캐시 | | | |
| 검색엔진 | | | |
| 파일 스토리지 | | | |
## 4. 인프라 및 배포
### 호스팅
- **프론트엔드**:
- **백엔드**:
### CI/CD
- **플랫폼**:
- **스테이지**: dev → staging → production
### 모니터링
- **APM**:
- **로깅**:
- **애널리틱스**:
### 컨테이너
- **Docker**: Yes/No
- **오케스트레이션**:
## 5. 외부 API 및 서비스
| 서비스 | 선택 | 용도 | API 문서 |
|--------|------|------|---------|
| 인증 | | | |
| 결제 | | | |
| 이메일/SMS | | | |
| AI/ML | | | |
## 6. 개발 도구
| 도구 | 선택 |
|------|------|
| IDE | |
| 패키지 매니저 | |
| 모노레포 | |
| 린팅 | |
| 포매팅 | |
| 유닛 테스트 | |
| E2E 테스트 | |
| 문서화 | |
What ships with it
2 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.
- 5d ago First seen · 194 lines · 72 tokens per session scan A 4eb7b6bae7fe
tech-stack is a skill published in the GitHub repository rungchan2/frontend-skills (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 72 tokens to every session and 1,387 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…