Borrowing it
Nothing to install: this file belongs to Piyush8296/claude-workspace. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Piyush8296/claude-workspace/main/.claude/commands/deploy.mdgit clone --depth 1 https://github.com/Piyush8296/claude-workspaceWrote 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/commands/piyush8296/claude-workspace/deploy)<a href="https://agentmods.dev/commands/piyush8296/claude-workspace/deploy"><img src="https://agentmods.dev/badge/commands/piyush8296/claude-workspace/deploy/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/commands/piyush8296/claude-workspace/deploy"><img src="https://agentmods.dev/badge/commands/piyush8296/claude-workspace/deploy.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00005 | $0.00789 |
| Opus 5.5 | $0.00002 | $0.00316 |
| Sonnet 5.5 | $0.00001 | $0.00158 |
| Haiku 4.5 | $0.00001 | $0.00079 |
Grade A, and why
deploy 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 1mo 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy Readiness Check
Run a comprehensive pre-deployment verification before shipping to production.
Steps
1. Environment Validation
- Verify all required environment variables are set for the target environment
- Check
.env.exampleis in sync with actual.envusage across the codebase - Confirm no secrets or API keys are hardcoded in source files
- Validate environment-specific configs (API URLs, feature flags, analytics IDs)
2. Build Verification
- Run
npm run build(or equivalent) and confirm zero errors - Check bundle size against budgets: main JS < 200KB gzipped, CSS < 50KB gzipped
- Verify no console.log or debugger statements in production code
- Confirm source maps are configured correctly (generated but not publicly served)
- Check for any TypeScript
@ts-ignoreoranytype escapes added in this release
3. Test Suite
- Run full test suite:
npm test -- --coverage - Confirm coverage thresholds are met (statements > 80%, branches > 75%)
- Run E2E tests against staging:
npm run test:e2e - Verify no skipped tests (
.skip) were left from debugging
4. Database & API
- List any pending database migrations and verify they are reversible
- Confirm API versioning: no breaking changes to existing endpoints
- Check that new API endpoints have rate limiting configured
- Verify webhook endpoints have retry/idempotency handling
5. Feature Flags
- List all feature flags modified in this release
- Confirm flags default to OFF for new features
- Document flag cleanup plan for flags older than 30 days
- Verify flag evaluation doesn't block critical render path
6. Performance Check
- Run Lighthouse CI and confirm scores: Performance > 90, Accessibility > 95
- Check Core Web Vitals: LCP < 2.5s, INP < 200ms, CLS < 0.1
- Verify no render-blocking resources added
- Confirm images are optimized (WebP/AVIF with fallbacks, proper sizing)
7. Security Scan
- Run
npm auditand confirm no high/critical vulnerabilities - Check CSP headers are configured for new external resources
- Verify authentication flows work end-to-end
- Confirm CORS policies are correct for the target environment
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.
- 1mo ago First seen · 87 lines · 5 tokens per session scan A 260285165e72
deploy is a command published in the GitHub repository Piyush8296/claude-workspace (2 stars, last pushed 6mo ago), licensed MIT. It adds 5 tokens to every session and 789 once invoked, about $0.0000 per session on Opus 5.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-31.
Other commands, from other repositories
firebase-publish
Create or reuse a Firebase project, configure Hosting, and deploy the current static site. Never deletes.
setup-cdn-optimization
Command "setup-cdn-optimization" from qdhenry/Claude-Command-Suite, covering setup cdn optimization and instructions.
deploy
Deploy the current project to Vercel.
cfo
Chief Financial Officer review — cloud cost optimization, resource efficiency, billing logic, compute waste.
flow-nexus-app-store
Browse, publish, and deploy applications.
watch
You are executing the /hydra:watch command. Live monitoring of all background agents with real-time status updates.