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/danielvm-git/bigpowers/deploynpx skills add danielvm-git/bigpowers --skill deploygit clone --depth 1 https://github.com/danielvm-git/bigpowersWhat 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.00055 | $0.01855 |
| Opus 5 | $0.00028 | $0.00928 |
| Sonnet 5 | $0.00011 | $0.00371 |
| Haiku 4.5 | $0.00006 | $0.00186 |
Grade A, and why
deploy 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 yesterday.
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.
| Smoke | `curl -sSf $DEPLOY_URL` as baseline health check | Non-200: report failure | How it starts
The opening of the file, as written. The whole thing — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy
HARD GATE — Do not deploy without running tests first. Run
testor your CI suite before this skill.HARD GATE — Use this skill from a CI/CD pipeline or post-merge on
main/master. Never deploy from a feature branch.HARD GATE — The deploy skill orchestrates deployment; the
smoke-testskill validates post-deploy health. Chain them:deploy → smoke-test.
Orchestrate a full build-to-deployment pipeline: build the artifact, verify it exists and is non-empty, invoke a platform deploy tool (MCP or CLI), poll until the deploy completes or times out, then run a baseline smoke test against the live URL.
Pipeline Stages
build → verify artifact → deploy → wait/retry → smoke
| Stage | Description | Failure mode |
|---|---|---|
| Build | Execute the project's build command | Non-zero exit: report build error |
| Verify | Check artifact exists and is non-empty | Missing/empty: report artifact path |
| Deploy | Invoke platform deploy tool (MCP, Vercel CLI, rsync, etc.) | Non-zero exit: report deploy error |
| Wait | Poll deploy status every 30s up to DEPLOY_TIMEOUT (default 5 min) |
Timeout: report exceeded |
| Smoke | curl -sSf $DEPLOY_URL as baseline health check |
Non-200: report failure |
Process
1. Detect build command
Read project manifest files in order to determine the build command:
| Manifest | Build command |
|---|---|
package.json |
npm run build (or scripts.build value) |
Cargo.toml |
cargo build --release |
pyproject.toml / setup.py |
Depends on build backend (poetry build, pip install -e ., etc.) |
Makefile |
make build or first target named build |
AGENTS.md / CLAUDE.md |
Look for build: in project commands section |
If no manifest is found, prompt the user with: "No detected build command. Pass --build 'npm run build' or specify the command."
2. Build the artifact
npm run build
Or the detected command from step 1. If the build fails, exit non-zero and report the build output.
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.
- yesterday First seen · 199 lines · 55 tokens per session scan A 05050bd6cb0b
deploy is a skill published in the GitHub repository danielvm-git/bigpowers (156 stars, last pushed 25d ago), licensed MIT. It adds 55 tokens to every session and 1,855 once invoked, about $0.0003 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-30.
Other skills, from other repositories
shared/tech-stack-detection
检测项目技术栈的通用方法，通过分析配置文件识别语言、框架、工具链.
devops/changelog-generation
自动生成 CHANGELOG，基于 git 提交历史和 pipeline 产物信息，遵循 Conventional Commits 和 Keep a Changelog 规范.
boss
可审计的 agent 团队：BMAD 全自动研发流水线编排器。编排 9 个专业 Agent（PM、架构师、UI Designer、Tech Lead、Scrum Master、Frontend、Backend、QA、DevOps）从需求到部署，每一步都有事件溯源 + 不可绕过门禁 + 确定性 eval——可验证测试真跑、门禁真过。支持单环节切片命令（/boss:plan /review /qa /ship）与无 CLI 纯 Markdown 降级。 Triggers: 'boss mode', '/boss', '全自动开发', '从需求到部署', '帮我做一个', 'build this', 'ship it', '全流程'…
debloat
Compress an artifact that has accreted into bloat — padding, over-qualification, fused sentences, walls of enumeration, adjacent restatement — down to its load-bearing density, meaning preserved. Use when prose is correct and current but has grown verbose or patched-over and you want it tight without a full rewrite.
bmad-dev-story
Execute story implementation following a context filled story spec file. Use when the user says "dev this story [story file]" or "implement the next story in the sprint plan".
bmad-validate-prd
Validate a PRD against standards. Use when the user says "validate this PRD" or "run PRD validation".