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.
git clone --depth 1 https://github.com/build-with-dhiraj/ai-workflow-framework-portability-kitWrote 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/build-with-dhiraj/ai-workflow-framework-portability-kit/deploy)<a href="https://agentmods.dev/commands/build-with-dhiraj/ai-workflow-framework-portability-kit/deploy"><img src="https://agentmods.dev/badge/commands/build-with-dhiraj/ai-workflow-framework-portability-kit/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/build-with-dhiraj/ai-workflow-framework-portability-kit/deploy"><img src="https://agentmods.dev/badge/commands/build-with-dhiraj/ai-workflow-framework-portability-kit/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.00029 | $0.01842 |
| Opus 5.5 | $0.00012 | $0.00737 |
| Sonnet 5.5 | $0.00006 | $0.00368 |
| Haiku 4.5 | $0.00003 | $0.00184 |
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 26d 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy to Vercel
Deploy the current project to Vercel using the CLI, with preflight safety checks, explicit production confirmation, and post-deploy verification.
Preflight
Run these checks before any deployment. Stop on failure and print actionable guidance.
- CLI available? — Confirm
vercelis on PATH.- If missing:
npm i -g vercel(orpnpm add -g vercel/bun add -g vercel).
- If missing:
- Project linked? — Check for
.vercel/project.jsonin the current directory or nearest parent.- If not found: run
vercel linkinteractively, then re-run/deploy.
- If not found: run
- Monorepo detection — Look for
turbo.jsonorpnpm-workspace.yamlat the repo root.- If detected: confirm which package is targeted. If ambiguous, ask the user before proceeding.
- Uncommitted changes — Run
git status --porcelain.- If output is non-empty: warn the user that uncommitted changes will not be included in the deploy. Ask whether to continue or commit first.
- If not a git repo, skip this check.
- Observability preflight (production deploys only) —
Before promoting to production, verify observability readiness:
- Drains check: Query configured drains via MCP
list_drainsor REST API. If no drains are configured on a Pro/Enterprise plan, warn:⚠️ No drains configured. Production errors won't be forwarded to external monitoring. Configure drains via Dashboard or REST API before promoting. See
⤳ skill: observability. - Errored drains: If any drain is in error state, warn and suggest remediation before deploying:
⚠️ Drain "" is errored. Fix or recreate before production deploy to avoid monitoring gaps.
- Error monitoring: Check that at least one of these is in place: configured drains, an error tracking integration (e.g., Sentry, Datadog via
vercel integration ls), or@vercel/analyticsin the project. - These are warnings, not blockers — the user may proceed after acknowledgment.
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.
- 26d ago First seen · 198 lines · 29 tokens per session scan A b45ce44b2db2
deploy is a command published in the GitHub repository build-with-dhiraj/ai-workflow-framework-portability-kit (5 stars, last pushed 13d ago), licensed MIT. It adds 29 tokens to every session and 1,842 once invoked, about $0.0001 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-09-21.
Other commands, from other repositories
ship-deployment
This file contains platform-specific deployment and validation for /ship.
OPSX: Archive
Archive a completed change in the experimental workflow.
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
resolve-dependabot-prs
Triage open Dependabot PRs, return a quick risk/action summary table, then enter planning mode with an ordered rebase→merge→follow-up→resume resolution plan.
update-check.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
firebase-publish
Create or reuse a Firebase project, configure Hosting, and deploy the current static site. Never deletes.