Borrowing it
Nothing to install: this file belongs to agno-agi/agentos-render. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/agno-agi/agentos-render/main/.agents/skills/deploy-platform/SKILL.mdgit clone --depth 1 https://github.com/agno-agi/agentos-renderWrote 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/agno-agi/agentos-render/deploy-platform)<a href="https://agentmods.dev/skills/agno-agi/agentos-render/deploy-platform"><img src="https://agentmods.dev/badge/skills/agno-agi/agentos-render/deploy-platform/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/agno-agi/agentos-render/deploy-platform"><img src="https://agentmods.dev/badge/skills/agno-agi/agentos-render/deploy-platform.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.00039 | $0.01196 |
| Opus 5.5 | $0.00016 | $0.00478 |
| Sonnet 5.5 | $0.00008 | $0.00239 |
| Haiku 4.5 | $0.00004 | $0.00120 |
Grade A, and why
deploy-platform 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 today.
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.
This is a copy
100% identical to deploy-platform — 158 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy the Platform on Render
Help the user deploy their application through the Render dashboard. Prepare the
repository, guide the Blueprint setup, and verify the authenticated application.
Read AGENTS.md, render.yaml, and the application's settings.
Use the current Render Blueprint docs
when dashboard details are uncertain.
1. Prepare the GitHub repository
Inspect the Git remotes, branch, and application changes. Reuse the user's repository
if one exists. Otherwise, establish the GitHub owner, repository name, and visibility,
then help create it using the available GitHub integration or gh repo create.
Use a private repository unless the user wants it public.
Preserve the template remote as upstream when making the user's repository
origin. Review the files to publish, exclude credentials and local artifacts,
commit the application, and push the intended deployment branch. Verify that the
pushed branch includes the user's agents, Dockerfile, and root render.yaml.
Help the user grant Render's GitHub connection access to this repository.
The Blueprint creates an AgentOS project and Production environment.
Set projects[0].name to the user's application name before pushing if they want
a different project name.
2. Deploy the Blueprint
Identify the intended Render workspace and any existing deployment. Reuse its Blueprint, API service, and database when present; continue to configuration below. For a new deployment, guide the user through Render:
- Choose New → Blueprint and connect their GitHub repository.
- Select the deployment branch and root
render.yaml. - Enter
OPENAI_API_KEYand setRUNTIME_ENVtodevfor initial setup. - Review the resources and billing, then choose Deploy Blueprint.
- Wait for the API to become live and copy its public HTTPS URL.
Start with the Blueprint's one always-on API instance with 1 CPU and 2 GB RAM
(1c-2g) and PostgreSQL 18 database.
Confirm both use Virginia (region: virginia) before deploying.
Preserve the database references. Initial setup runs without authentication;
continue directly to securing the application below. For an existing secured
deployment, keep RUNTIME_ENV=prd.
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.
- today Changed · +1 lines 61609b5221cb
- 2d ago Changed · +14 lines · +3 tokens per session bf102f9ae34b
- 3d ago Changed · -2 lines 50762309e28e
- 6d ago Changed · +2 lines · -46 tokens per session 5b9f8cc35fc1
- 8d ago Changed f25f860f21b9
- 2mo ago First seen · 91 lines · 82 tokens per session scan A 2f097e6cb2e8
deploy-platform is a skill published in the GitHub repository agno-agi/agentos-render (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 39 tokens to every session and 1,196 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to deploy-platform, differing in 158 lines, and is treated as a copy.
Other skills, from other repositories
render
Use when deploying or fixing an app on Render — web services, background workers, cron jobs, private services, managed Postgres and Key-Value, and especially the render.yaml Blueprint. Covers deploys that fail with no open ports detected, 502s on first deploy, free-tier cold starts, and a free Postgres about to expire…
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running security audits (auditcluster.sh), enforcing Network Policies (default-deny and Dataplane V2 logging), isolating high-risk pods inside GKE Sandbox (gVisor), enforcing Pod…
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 generating K8s YAML manifests (use gke-manifest-generation) or disaster recovery…
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…
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".