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 rules/danielvm-git/bigpowers/deploygit clone --depth 1 https://github.com/danielvm-git/bigpowersWrote 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/rules/danielvm-git/bigpowers/deploy)<a href="https://agentmods.dev/rules/danielvm-git/bigpowers/deploy"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/deploy.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.00053 | $0.01851 |
| Opus 5 | $0.00026 | $0.00925 |
| Sonnet 5 | $0.00011 | $0.00370 |
| Haiku 4.5 | $0.00005 | $0.00185 |
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 today.
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 — 198 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.
- today First seen · 198 lines · 53 tokens per session scan A 21b793bd4db9
deploy is a cursor rule published in the GitHub repository danielvm-git/bigpowers (162 stars, last pushed 2d ago), licensed MIT. It adds 53 tokens to every session and 1,851 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-09-03.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
app-router-patterns
Next.js 14+ App Router patterns — Server Components, Client Components, Route Handlers, Server Actions, and metadata API.
context-os
ContextOS rules for context-os.
database
Database architecture, schema design, Prisma, Drizzle ORM, indexing strategies, migrations, and N+1 query resolution.
vue
Rules for Vue (2 and 3) single-file components.
nextjs
ContextOS rules for nextjs.