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 skills/vpeetla-ai/multi-agent-system-pattern/deploy-vercel-rendernpx skills add vpeetla-ai/multi-agent-system-pattern --skill deploy-vercel-rendergit clone --depth 1 https://github.com/vpeetla-ai/multi-agent-system-patternWrote 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/skills/vpeetla-ai/multi-agent-system-pattern/deploy-vercel-render)<a href="https://agentmods.dev/skills/vpeetla-ai/multi-agent-system-pattern/deploy-vercel-render"><img src="https://agentmods.dev/badge/skills/vpeetla-ai/multi-agent-system-pattern/deploy-vercel-render.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.00055 | $0.00381 |
| Opus 5 | $0.00028 | $0.00191 |
| Sonnet 5 | $0.00011 | $0.00076 |
| Haiku 4.5 | $0.00006 | $0.00038 |
Grade A, and why
deploy-vercel-render 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 https://loopforge-api.onrender.com/health Copies of this mod
1 near-identical copy found in the catalogue:
- deploy-vercel-render — 100% identical, 0 lines differ
What it actually says
Deploy: Vercel + Render
Standard split
| Layer | Host | Config |
|---|---|---|
| UI demo | Vercel | vercel.json, config.js API URL |
| Python API | Render | render.yaml, Dockerfile |
Render free tier
# render.yaml
plan: free # REQUIRED — avoids credit card prompt
Env vars (Render)
GROQ_API_KEY,GITHUB_TOKEN(LoopForge)AEGISAI_API_BASE_URL(gateway integrations)- Never commit secrets — Render dashboard only
Vercel
- Deploy from subfolder:
cd demo && vercel --prod - Point
LOOPFORGE_API/API_BASEinconfig.jsto Render URL
Health checks
curl https://loopforge-api.onrender.com/health
Cold start
- Render free spins down ~15min idle — document in README
- Vercel edge is always warm for static
Reference deploys
| Project | Demo | API |
|---|---|---|
| LoopForge | demo-omega-taupe.vercel.app | loopforge-api.onrender.com |
| Enterprise RAG | enterprise-rag-platform.vercel.app | — |
| VAP | venkat-ai-platform.vercel.app | — |
Docs
Each repo: docs/DEPLOY.md with exact commands and env table
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 · 58 lines · 55 tokens per session scan A 2c0ffe439415
deploy-vercel-render is a skill published in the GitHub repository vpeetla-ai/multi-agent-system-pattern (2 stars, last pushed today), licensed MIT. It adds 55 tokens to every session and 381 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-08-31.
Other skills, from other repositories
spec-code-review
Structured code review for bugs, regressions, tests, and standards. Report-only by default; apply fixes only when the current user or upstream caller explicitly requests review-and-fix. mode:agent is always report-only.
spec-compound-refresh
Refresh docs/solutions learnings against the current codebase. Use when auditing stale, overlapping, superseded, or drifted learnings; avoid general refactor, debugging, or code review unless docs/solutions is explicit.
spec-brainstorm
Explore vague or ambitious ideas into a right-sized requirements-only unified plan. Use when the user wants to brainstorm, think through scope, decide what to build, or needs collaborative product framing before planning. Also use when the user must scope work in territory they say they do not know ("I know nothing…
spec-debug
Diagnosis loop for bugs and failing behavior. Use for errors, stack traces, regressions, failed tests, issue-tracker bugs, stuck investigations after failed fixes, or asks to debug/fix a bug.
spec-commit-push-pr
Internal landing helper for public workflows that already hold explicit commit and landing authorization; commits scoped changes, pushes, and creates or updates a PR with a value-first description.
spec-lfg
Run the full hands-off engineering pipeline from planning through a green PR. Use only when the current user explicitly requests spec-lfg or selects an option that clearly states it will commit, push, open a PR, and watch CI.