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/bootstrap)<a href="https://agentmods.dev/commands/build-with-dhiraj/ai-workflow-framework-portability-kit/bootstrap"><img src="https://agentmods.dev/badge/commands/build-with-dhiraj/ai-workflow-framework-portability-kit/bootstrap/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/bootstrap"><img src="https://agentmods.dev/badge/commands/build-with-dhiraj/ai-workflow-framework-portability-kit/bootstrap.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.00031 | $0.01420 |
| Opus 5.5 | $0.00012 | $0.00568 |
| Sonnet 5.5 | $0.00006 | $0.00284 |
| Haiku 4.5 | $0.00003 | $0.00142 |
Grade A, and why
bootstrap 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 25d 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vercel Project Bootstrap
Run a deterministic bootstrap flow for new or partially configured repositories.
Preflight
- Confirm Vercel CLI is installed and authenticated.
vercel --version
vercel whoami
- Confirm repo linkage by checking
.vercel/project.json. - If not linked, inspect available teams/projects before asking the user to choose:
vercel teams ls
vercel projects ls --scope <team>
vercel link --yes --scope <team> --project <project>
- Find the env template in priority order:
.env.example,.env.sample,.env.template. - Create local env file if missing:
cp .env.example .env.local
- Detect package manager and available scripts (
db:push,db:seed,db:migrate,db:generate,dev) frompackage.json. - Inspect auth/database signals (
prisma/schema.prisma,drizzle.config.*,auth.*,src/**/auth.*) to scope bootstrap details.
Stop with clear guidance if CLI auth or linkage fails.
Plan
Execute in this order:
- Preflight validation and project linking.
- Resource provisioning (prefer Vercel-managed Neon integration).
- Secret/bootstrap env setup (
AUTH_SECRET, env pull, key verification). - Application bootstrap (
db:*thendev) only after env checks pass.
- Do not run
db:push,db:migrate,db:seed, ordevuntil Vercel linking is complete and env keys are verified. - Prefer Vercel-managed provisioning (
vercel integration ...) for shared resources. - Use provider CLIs only as fallback when Vercel integration flow is unavailable.
- Never echo secret values in terminal output, logs, or summaries.
Commands
1. Link + local env template
Copy the first matching template file only if .env.local does not exist:
cp .env.example .env.local
If .env.example is absent, use .env.sample or .env.template.
2. Provision Postgres
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.
- 25d ago First seen · 184 lines · 31 tokens per session scan A e26a1f7aa23a
bootstrap is a command published in the GitHub repository build-with-dhiraj/ai-workflow-framework-portability-kit (5 stars, last pushed 12d ago), licensed MIT. It adds 31 tokens to every session and 1,420 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
p3-data-model
Designs the Data Model with entities and relationships as well as the API design with interface specification. The result is DATAMODEL.md and APISPEC.md as the binding foundation for implementation.
sparc-post-deployment-monitoring-mode
📈 Deployment Monitor - You observe the system post-launch, collecting performance, logs, and user feedback. You flag reg...
opsx-sync
Sync delta specs from a change to main specs.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.