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/render-oss/render-plugin-claude-code/render-migrate-from-herokunpx skills add render-oss/render-plugin-claude-code --skill render-migrate-from-herokugit clone --depth 1 https://github.com/render-oss/render-plugin-claude-codeWhat 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.00100 | $0.04052 |
| Opus 5 | $0.00050 | $0.02026 |
| Sonnet 5 | $0.00020 | $0.00810 |
| Haiku 4.5 | $0.00010 | $0.00405 |
Grade C, and why
render-migrate-from-heroku scanned grade C with 2 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 2d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
- Linux/macOS: `curl -fsSL https://raw.githubusercontent.com/render-oss/cli/main/bin/install.sh | sh` Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Linux/macOS: `curl -fsSL https://raw.githubusercontent.com/render-oss/cli/main/bin/install.sh | sh` This is a copy
97% identical to render-migrate-from-heroku — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 313 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Heroku to Render Migration
Migrate from Heroku to Render by reading local project files first, then optionally enriching with live Heroku data via MCP.
Prerequisites Check
Before starting, verify what's available:
- Local project files (required) — confirm the current directory contains a Heroku app (look for
Procfile,app.json,package.json,requirements.txt,Gemfile,go.mod, or similar) - Render MCP (recommended) — check if
list_servicestool is available. Required for MCP Direct Creation (Step 3B) and automated verification (Step 6). Not required for the Blueprint path — the Render CLI and Dashboard handle generation, validation, and deployment. - Heroku MCP (optional) — check if
list_appstool is available
If Render MCP is missing and the user needs it, guide them through setup using the MCP setup guide. If Heroku MCP is missing, note that config var values and add-on plan details will need to be provided manually.
Migration Workflow
Execute steps in order. Present findings to the user and get confirmation before creating any resources.
Step 1: Inventory Heroku App
Gather app details from local files first, then supplement with Heroku MCP if available.
1a. Read local project files (always)
Read these files from the repo to determine runtime, commands, and dependencies:
| File | What it tells you |
|---|---|
Procfile |
Process types and start commands (web, worker, clock, release) |
package.json |
Node.js runtime, build scripts, framework deps (Next.js, React, etc.) |
requirements.txt / Pipfile / pyproject.toml |
Python runtime, dependencies (Django, Flask, etc.) |
Gemfile |
Ruby runtime, dependencies (Rails, Sidekiq, etc.) |
go.mod |
Go runtime |
Cargo.toml |
Rust runtime |
app.json |
Declared add-ons, env var descriptions, buildpacks |
runtime.txt |
Pinned runtime version |
static.json |
Static site indicator |
yarn.lock / pnpm-lock.yaml |
Package manager (affects build command) |
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 313 lines · 100 tokens per session scan C 03634b5a7ad3
render-migrate-from-heroku is a skill published in the GitHub repository render-oss/render-plugin-claude-code (0 stars, last pushed 14d ago), licensed MIT. It adds 100 tokens to every session and 4,052 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). It is 97% identical to render-migrate-from-heroku, differing in 8 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.