Borrowing it
Nothing to install: this file belongs to agno-agi/agentos-docker. 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-docker/main/.agents/skills/deploy-platform/SKILL.mdgit clone --depth 1 https://github.com/agno-agi/agentos-dockerWrote 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-docker/deploy-platform)<a href="https://agentmods.dev/skills/agno-agi/agentos-docker/deploy-platform"><img src="https://agentmods.dev/badge/skills/agno-agi/agentos-docker/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-docker/deploy-platform"><img src="https://agentmods.dev/badge/skills/agno-agi/agentos-docker/deploy-platform.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Tool Misuse · line 64 Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.Fix: Override unsafe defaults with secure settings (verify=True, auth required, restrictive permissions). Review and harden all tool configurations.
- medium MCP Rug Pull · line 84 uvx/uv tool run commands without ==version create a rug-pull risk.Fix: Pin the version: uvx package-name==1.2.3
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.
Copies of this mod
2 near-identical copies found in the catalogue:
- deploy-platform — 100% identical, 4 lines differ
- deploy-platform — 100% identical, 158 lines differ
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 f28ed50c9ce3
- 3d ago Changed · -2 lines 5b6c1af1e37f
- 6d ago Changed · +2 lines · -46 tokens per session 7cd3e0d33563
- 7d ago Changed ce5e30114f7e
- 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-docker (14 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
tianji-worker
Use when creating, testing, deploying, invoking, debugging, scheduling, pausing, or rolling back Tianji Workers, or managing their environment variables and shared modules.
ecspresso
ECS deployment tool - deploy, manage, and troubleshoot ECS services.
cloudflare-deploy
Deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services. Use when the user asks to deploy, host, publish, or set up a project on Cloudflare.
vercel-deploy
Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".
k8s-dev-deploy
Build, push, and deploy Kurtosis dev images to a Kubernetes cluster without creating a release. Rebuilds engine, core, and files-artifacts-expander as multi-arch Docker images with a unique tag, pushes to the logged-in user's Docker Hub, and restarts the engine. Use when testing local code changes on a k8s cluster.
cluster-manage
Manage Kurtosis cluster settings. Switch between Docker and Kubernetes backends, list available clusters, and configure which cluster Kurtosis uses. Use when you need to change where Kurtosis runs enclaves.