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 commands/sawadari/requirements-mcp-server/deploygit clone --depth 1 https://github.com/sawadari/requirements-mcp-serverWrote 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/sawadari/requirements-mcp-server/deploy)<a href="https://agentmods.dev/commands/sawadari/requirements-mcp-server/deploy"><img src="https://agentmods.dev/badge/commands/sawadari/requirements-mcp-server/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.00008 | $0.01988 |
| Opus 5 | $0.00004 | $0.00994 |
| Sonnet 5 | $0.00002 | $0.00398 |
| Haiku 4.5 | $0.00001 | $0.00199 |
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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -f https://your-app.web.app/health How it starts
The opening of the file, as written. The whole thing — 367 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy Command
DeploymentAgentを使用してアプリケーションをデプロイします。
使用方法
/deploy [environment]
パラメータ
environment(オプション): デプロイ環境staging(デフォルト): ステージング環境production: プロダクション環境
実行内容
1. Pre-Deployment Checks
# TypeScriptコンパイル確認
npm run typecheck
# テスト実行
npm test -- --run
# ビルド実行
npm run build
2. Firebase Deploy
# Staging
firebase deploy --only hosting:staging
# Production (確認プロンプト付き)
firebase deploy --only hosting:production
3. Health Check
デプロイ後、ヘルスチェックURLに自動アクセスして動作確認:
curl -f https://your-app.web.app/health
4. Rollback (失敗時)
ヘルスチェックが失敗した場合、自動的に前のバージョンにロールバック:
firebase hosting:rollback
デプロイフロー
graph TD
A[/deploy実行] --> B[Pre-deployment Checks]
B --> C{テスト合格?}
C -->|No| D[エラー: デプロイ中止]
C -->|Yes| E[ビルド実行]
E --> F[Firebase Deploy]
F --> G[Health Check]
G --> H{正常?}
H -->|No| I[自動Rollback]
H -->|Yes| J[デプロイ完了]
I --> K[Tech Leadにエスカレーション]
必要な環境変数
# .env
FIREBASE_PROJECT_ID=your-firebase-project-id
FIREBASE_TOKEN=your-firebase-token # CI/CD用
Firebase Tokenの取得方法
# ローカル開発
firebase login
# CI/CD用トークン
firebase login:ci
# 表示されたトークンを FIREBASE_TOKEN に設定
GitHub Secretsの設定
GitHub Actions経由でデプロイする場合:
- Repository Settings → Secrets and variables → Actions
- 以下のSecretsを追加:
FIREBASE_TOKEN: Firebase CI tokenANTHROPIC_API_KEY: Claude API key (既存)
デプロイ設定
firebase.json
{
"hosting": [
{
"target": "staging",
"public": "dist",
"ignore": ["firebase.json", "**/.*", "**/node_modules/**"],
"rewrites": [
{
"source": "**",
"destination": "/index.html"
}
]
},
{
"target": "production",
"public": "dist",
"ignore": ["firebase.json", "**/.*", "**/node_modules/**"],
"rewrites": [
{
"source": "**",
"destination": "/index.html"
}
]
}
]
}
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.
- 4d ago First seen · 367 lines · 8 tokens per session scan A 2f0a62223881
deploy is a command published in the GitHub repository sawadari/requirements-mcp-server (2 stars, last pushed 10mo ago), licensed MIT. It adds 8 tokens to every session and 1,988 once invoked, about $0.0000 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-31.
Other commands, from other repositories
deploy
Build, test, deploy with staged rollout.
deploy
Deploy a frontend (React, Next.js, or static HTML) to a live URL on Butterbase.
cf-scaffold-project
Scaffold a Cloudflare project — Worker, Pages, or Worker+D1+R2 starter — with Wrangler config, Terraform skeleton, and GitHub Actions deploy using scoped API tokens.
scan
Scan AWS account for cost optimization.
finops-feedback
Step 5 (Feedback Loop & Celebration) — measure realized against projected savings, compute a labelled Cloud Entropy proxy, close the opportunity, and emit at least one new idea or policy update so the loop actually closes. Applies the double-loop gate. Mutates on the closure path.
run-panguweather
Guide the user through running PanguWeather end-to-end on an AMD cluster.