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 skills add cass-2003/local-workflow-skill --skill render-migrate-from-herokugit clone --depth 1 https://github.com/cass-2003/local-workflow-skillWrote 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/cass-2003/local-workflow-skill/render-migrate-from-heroku)<a href="https://agentmods.dev/skills/cass-2003/local-workflow-skill/render-migrate-from-heroku"><img src="https://agentmods.dev/badge/skills/cass-2003/local-workflow-skill/render-migrate-from-heroku/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/skills/cass-2003/local-workflow-skill/render-migrate-from-heroku"><img src="https://agentmods.dev/badge/skills/cass-2003/local-workflow-skill/render-migrate-from-heroku.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.00100 | $0.03989 |
| Opus 5 | $0.00050 | $0.01995 |
| Sonnet 5 | $0.00020 | $0.00798 |
| Haiku 4.5 | $0.00010 | $0.00399 |
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 6d 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 — 14 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 — 307 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
8 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.
- 6d ago First seen · 307 lines · 100 tokens per session scan C a8be961783c5
render-migrate-from-heroku is a skill published in the GitHub repository cass-2003/local-workflow-skill (12 stars, last pushed 2mo ago), licensed MIT. It adds 100 tokens to every session and 3,989 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 14 lines, and is treated as a copy.
Other skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…