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 skills add bam-bam-2/solo-skills --skill workshop-prepgit clone --depth 1 https://github.com/bam-bam-2/solo-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/bam-bam-2/solo-skills/workshop-prep)<a href="https://agentmods.dev/skills/bam-bam-2/solo-skills/workshop-prep"><img src="https://agentmods.dev/badge/skills/bam-bam-2/solo-skills/workshop-prep/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/bam-bam-2/solo-skills/workshop-prep"><img src="https://agentmods.dev/badge/skills/bam-bam-2/solo-skills/workshop-prep.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 9 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 210 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 233 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 261 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 378 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 262 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Tool Misuse · line 401 Tool calls are chained to bypass individual safety checks or escalate capabilities beyond what any single tool call would allow.Fix: Limit tool chaining depth and validate the output of each tool before passing it to the next. Require explicit user approval for multi-step chains.
- medium Data Exfiltration · line 227 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 250 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- low Supply Chain · line 401 Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.Fix: Avoid downloading and executing remote scripts. Use trusted packages from PyPI/npm. If remote fetch is required, verify checksums and use HTTPS.
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.1 | $0.00114 | $0.04432 |
| Opus 5 | $0.00057 | $0.02216 |
| Sonnet 5 | $0.00023 | $0.00886 |
| Haiku 4.5 | $0.00011 | $0.00443 |
Grade C, and why
workshop-prep scanned grade C with 2 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 10d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -fsSL https://raw.githubusercontent.com/{username}/{스킬명}/main/install.sh | bash Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- 설치 방법 (curl/powershell 원클릭) How it starts
The opening of the file, as written. The whole thing — 417 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workshop Prep
Claude Code 바이브코딩 워크샵 사전 준비 퍼실리테이터.
Core Principles
- 참석자는 뭘 자동화해야 하는지, 뭐가 가능한지 모름
- 질문으로 생각을 이끌어내고, 예시로 가능성을 보여줌
- 한 번에 한 질문만, 수다 떠는 느낌으로
Workflow
Phase 0: Context7 설정 확인 (필수)
⚠️ Context7 API 키가 없으면 인터뷰를 시작할 수 없습니다.
스킬 시작 전 Context7 MCP 설정 여부 확인:
mcp_context7_resolve-library-id호출 시도- 실패 시 (API 키 미설정):
- 안내: "Context7 API 키가 필요해요! 제가 대신 설정해드릴게요 😊"
- API 키 발급 안내:
1. https://context7.com/dashboard 접속 2. GitHub 또는 Google로 로그인 3. API Key 복사 4. 여기에 붙여넣기 해주세요! - 사용자가 API 키를 붙여넣으면:
a.
~/.mcp.json파일 읽기 (없으면 생성) b.mcpServers.context7설정 추가:
c. 파일 저장 d. "설정 완료! Claude Code를 재시작해주세요. 재시작 후 다시 '워크샵 준비해줘'라고 말씀해주세요!""context7": { "command": "npx", "args": ["-y", "@upstash/context7-mcp", "--api-key", "{사용자가_입력한_키}"] } - Claude Code 재시작 필요 안내 (MCP 설정은 재시작해야 적용됨)
- 성공 시: Phase 1로 진행
진행 불가 안내:
- "외부 서비스 연동 가이드를 만들려면 Context7이 꼭 필요해요!"
- "API 키만 붙여넣어 주시면 제가 알아서 설정해드릴게요 👍"
Phase 1: Warmup
역할 파악. "지금 회사에서 어떤 일을 맡고 계세요?"로 시작.
- 꼬리질문: 하루가 어떻게 흘러가는지, 어떤 툴을 많이 쓰는지
Phase 2: Find Repetitive Tasks
구체적 예시와 함께 반복 업무 탐색. See examples.md for role-specific categories.
- 얼마나 자주? 한 번에 시간이 얼마나?
- 어디서 시작해서 어디서 끝나는지?
Phase 3: Map the Process
시작점 → 과정 → 결과물 순서로 파악.
- 시작점: 이 일이 시작되는 계기
- 과정: 그 다음 뭘 하는지, 어디서 뭘 여는지
- 결과물: 최종적으로 뭐가 나오는지, 어디에 공유하는지
Phase 4: Show Possibilities
맥락 파악 후 비슷한 자동화 사례 제시. See examples.md for role-specific automation examples.
Phase 4.5: Tech Detection
외부 연동 필요성 파악. Phase 3에서 파악한 "결과물 목적지"를 기반으로 질문.
핵심 질문:
- "이 결과물은 어디에 저장하거나 공유하세요?"
- "혹시 이메일로 보내거나, 슬랙에 올리거나, 드라이브에 저장하시나요?"
답변 분석: 사용자 답변에서 키워드를 감지하여 필요한 연동 도구 파악. See integrations.md for keyword-to-MCP mapping.
| 키워드 예시 | 연동 도구 |
|---|---|
| 이메일, 메일, Gmail | Google Workspace |
| 슬랙, Slack, 채널 | Slack |
| 드라이브, Drive, 파일 저장 | Google Workspace |
| 줌, Zoom, 녹화 | Zoom |
| 유튜브, 영상 업로드 | YouTube |
| 노션, Notion | Notion |
What ships with it
3 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.
- 10d ago First seen · 417 lines · 114 tokens per session scan C 4247af6a7b30
workshop-prep is a skill published in the GitHub repository bam-bam-2/solo-skills (362 stars, last pushed 6d ago), licensed MIT. It adds 114 tokens to every session and 4,432 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
gws-gmail
Gmail: Send, read, and manage email.
recipe-block-focus-time
Create recurring focus time blocks on Google Calendar to protect deep work hours.
recipe-create-vacation-responder
Enable a Gmail out-of-office auto-reply with a custom message and date range.
recipe-save-email-attachments
Find Gmail messages with attachments and save them to a Google Drive folder.
happiness-skill
A Chinese-language guide to happiness based on reducing unmet wants, focusing on the present, and treating happiness as a trainable skill.
post-build-flow
Handles workflow verification and setup after build-workflow succeeds, or when the message contains workflow-verification-follow-up or workflow-setup-required. Load after direct builds, when verificationReadiness requires action, or on orchestrator verify/setup follow-up turns.