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/echovic/boss-skill/tech-stack-detectionnpx skills add echoVic/boss-skill --skill tech-stack-detectiongit clone --depth 1 https://github.com/echoVic/boss-skillWhat 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.00029 | $0.02215 |
| Opus 5 | $0.00015 | $0.01107 |
| Sonnet 5 | $0.00006 | $0.00443 |
| Haiku 4.5 | $0.00003 | $0.00221 |
Grade A, and why
shared/tech-stack-detection 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 — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.
技术栈检测方法
适用场景
在进行技术选型、架构设计、代码生成前，需要先了解项目当前使用的技术栈，以便：
- 遵循项目现有的技术选择
- 生成符合项目规范的代码
- 避免引入不兼容的技术
检测方法
1. 检测配置文件
使用 Read 或 Glob 工具检测项目根目录的配置文件：
JavaScript/TypeScript 生态
| 文件 | 说明 | 检测内容 |
|---|---|---|
package.json |
Node.js 项目配置 | dependencies, devDependencies, scripts |
tsconfig.json |
TypeScript 配置 | 确认使用 TypeScript |
next.config.js |
Next.js 配置 | 确认使用 Next.js |
vite.config.js |
Vite 配置 | 确认使用 Vite |
nuxt.config.js |
Nuxt 配置 | 确认使用 Nuxt |
检测命令：
# 检测是否存在
ls package.json tsconfig.json next.config.js vite.config.js 2>/dev/null
# 读取 package.json
Read(file_path: "package.json")
关键依赖识别：
react: React 项目vue: Vue 项目next: Next.js 项目@angular/core: Angular 项目express: Express 后端fastify: Fastify 后端prisma: Prisma ORMtypeorm: TypeORM
Python 生态
| 文件 | 说明 | 检测内容 |
|---|---|---|
requirements.txt |
pip 依赖 | 依赖列表 |
pyproject.toml |
Poetry/PDM 配置 | 依赖和项目配置 |
Pipfile |
Pipenv 配置 | 依赖 |
setup.py |
包配置 | 项目元数据 |
关键依赖识别：
django: Django 项目flask: Flask 项目fastapi: FastAPI 项目sqlalchemy: SQLAlchemy ORMpytest: 使用 pytest 测试
Go 生态
| 文件 | 说明 | 检测内容 |
|---|---|---|
go.mod |
Go 模块配置 | 依赖和 Go 版本 |
go.sum |
依赖校验和 | 确认依赖锁定 |
关键依赖识别：
github.com/gin-gonic/gin: Gin 框架github.com/gofiber/fiber: Fiber 框架gorm.io/gorm: GORM ORM
Rust 生态
| 文件 | 说明 | 检测内容 |
|---|---|---|
Cargo.toml |
Cargo 配置 | 依赖和项目配置 |
Cargo.lock |
依赖锁定 | 确认依赖版本 |
关键依赖识别：
actix-web: Actix Web 框架axum: Axum 框架tokio: 异步运行时
Java/Kotlin 生态
| 文件 | 说明 | 检测内容 |
|---|---|---|
pom.xml |
Maven 配置 | 依赖和插件 |
build.gradle |
Gradle 配置 | 依赖和任务 |
关键依赖识别：
spring-boot-starter: Spring Boot 项目quarkus: Quarkus 项目micronaut: Micronaut 项目
Ruby 生态
| 文件 | 说明 | 检测内容 |
|---|---|---|
Gemfile |
Bundler 配置 | 依赖 |
Gemfile.lock |
依赖锁定 | 确认依赖版本 |
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 · 281 lines · 29 tokens per session scan A 617487d9e92d
shared/tech-stack-detection is a skill published in the GitHub repository echoVic/boss-skill (553 stars, last pushed 2d ago), licensed MIT. It adds 29 tokens to every session and 2,215 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-30.
Other skills, from other repositories
large-workspace-handling
To partition large workspaces (100+ files) into scoped subagent tasks when context is insufficient.
example-skill
Example skill template used for the CreateHub template. You should never use this skill directly as it is just a template made to be updated.
bmad-github-story-dev
Set up a git worktree/branch (or reuse the current one) and run BMAD dev-story end-to-end: auto-commits per task, PR creation, label updates. Use when the user invokes the SD menu code in bmad help, or asks to start implementing the next ready story, or asks to begin dev on a story.
bmad-github-story-sync
Reconcile GitHub state with BMAD files — detect merged PRs, mark stories done in sprint-status.yaml and story files, sync GitHub labels, and clean up worktrees and branches. Use when the user invokes the SS menu code in bmad help, or asks to sync BMAD with GitHub, or just merged a PR and wants BMAD updated.
bmad-github-story-create
Sync GitHub state then plan the next story end-to-end via the BMAD create-story flow. Detects blocking dependencies via GitHub labels and updates the GitHub issue label to ready. Use when the user invokes the SC menu code in bmad help, or asks to plan/create the next story, or asks to start the next BMAD story.
bmad-github-story-review
Run BMAD adversarial code review on the current story branch and push fixes. Does NOT mark the story done — the user merges the PR on GitHub. Use when the user invokes the SR menu code in bmad help, or asks to code-review the current story, or asks for an adversarial review of the open story PR.