Borrowing it
Nothing to install: this file belongs to agno-agi/agentos-modal. 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-modal/main/.agents/skills/deploy-platform/SKILL.mdgit clone --depth 1 https://github.com/agno-agi/agentos-modalWrote 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-modal/deploy-platform)<a href="https://agentmods.dev/skills/agno-agi/agentos-modal/deploy-platform"><img src="https://agentmods.dev/badge/skills/agno-agi/agentos-modal/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-modal/deploy-platform"><img src="https://agentmods.dev/badge/skills/agno-agi/agentos-modal/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.00036 | $0.01127 |
| Opus 5.5 | $0.00014 | $0.00451 |
| Sonnet 5.5 | $0.00007 | $0.00225 |
| Haiku 4.5 | $0.00004 | $0.00113 |
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 — 4 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy the Platform
Read AGENTS.md, the README deployment section, and this repository's deploy
configuration and scripts. Use those files to identify the provider and its exact
commands, required CLI versions, environment file, and teardown behavior.
Do not assume every template has deploy scripts or supports the same flags.
For Docker or an existing Kubernetes cluster, follow the repository's Compose or
Helm instructions.
Never print credentials or the MCP connect secret. The JWT verification key is public and may be shared to complete configuration.
1. Prepare
- Check the required tools and the authenticated provider account. Interactive logins belong in the user's terminal.
- Confirm the intended workspace, account, project, region, or cluster context before making changes. Use the inputs required by this repository's commands.
- Set up the project environment if the deploy scripts need it. Use the production
env file documented in the README; create it from
example.envonly if absent. Configure credentials without printing them. Check how the deploy scripts load settings rather than assuming they read.envor exported shell variables. - Keep production authentication enabled. Do not upload
RUNTIME_ENV=dev. ConfigureJWT_VERIFICATION_KEYor aJWT_JWKS_FILEavailable on the server. - If a sandbox is requested, configure its provider and
REPOSITORYinapp/sandbox.pyusing the sandbox setup guide. AgentCore needs an existing runtime, host AWS access, and an S3 checkpoint bucket. SetSANDBOX_ENABLED = Trueand the repository in code; setSANDBOX_PROVIDER=agentcore, runtime ARN and checkpoint bucket/prefix in the hosted environment. Do not attach an API disk or use PostgreSQL for checkpoint archives. Supply GitHub tokens at runtime and optional Bedrock overrides through the provider'senv. Never put secret values in source. - See docs/scaling.md for current scaling guidance.
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 b25ab05a57e5
- 3d ago Changed · -2 lines 3dfa719f21e1
- 6d ago Changed · +2 lines · -46 tokens per session bab679f379fa
- 8d ago Changed 96804eacd32b
- 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-modal (3 stars, last pushed today), licensed Apache-2.0. It adds 36 tokens to every session and 1,127 once invoked, about $0.0001 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 4 lines, and is treated as a copy.
Other skills, from other repositories
modal-serverless-gpu
Run approved CPU or GPU work through OpenScience computejob on the user's configured Modal account. Use for isolated scientific scripts, dependency provisioning, durable outputs, logs, status, cancellation, and recovery. Never invoke the Modal SDK or CLI directly.
modal
Use when running Python or GPU workloads serverlessly on Modal — modal.App, inline container Images, gpu= on @app.function, Volumes for weight caching, Cron schedules, ASGI endpoints, modal run vs serve vs deploy. NOT managed prediction APIs with no container of your own (that is replicate); NOT SSH-able GPU boxes…
modal-serverless-gpu
Serverless GPU cloud platform for running ML workloads. Use when you need on-demand GPU access without infrastructure management, deploying ML models as APIs, or running batch jobs with automatic scaling.
modal-serverless-gpu
Serverless GPU cloud platform for running ML workloads. Use when you need on-demand GPU access without infrastructure management, deploying ML models as APIs, or running batch jobs with automatic scaling.
modal-serverless-gpu
Serverless GPU cloud platform for running ML workloads. Use when you need on-demand GPU access without infrastructure management, deploying ML models as APIs, or running batch jobs with automatic scaling.
modal-serverless-gpu
Serverless GPU cloud platform for running ML workloads. Use when you need on-demand GPU access without infrastructure management, deploying ML models as APIs, or running batch jobs with automatic scaling.