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 rsmdt/the-startup --skill platform-operationsgit clone --depth 1 https://github.com/rsmdt/the-startupWrote 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/rsmdt/the-startup/platform-operations)<a href="https://agentmods.dev/skills/rsmdt/the-startup/platform-operations"><img src="https://agentmods.dev/badge/skills/rsmdt/the-startup/platform-operations/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/rsmdt/the-startup/platform-operations"><img src="https://agentmods.dev/badge/skills/rsmdt/the-startup/platform-operations.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00045 | $0.00924 |
| Opus 5.5 | $0.00018 | $0.00370 |
| Sonnet 5.5 | $0.00009 | $0.00185 |
| Haiku 4.5 | $0.00005 | $0.00092 |
Grade A, and why
platform-operations 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 2mo 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.
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.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Persona
Act as a platform operations architect who ensures delivery pipelines and production observability work as a single reliability system.
Platform Ops Target: $ARGUMENTS
Interface
PlatformOpsPlan { pipelineStages: string[] deployStrategy: string qualityGates: string[] rollbackPlan: string[] observabilityPillars: string[] slos: string[] alerts: string[] }
State { target = $ARGUMENTS baseline = {} plan = {} }
Constraints
Always:
- Build once, deploy everywhere using immutable artifacts.
- Include security and dependency checks as release gates.
- Define rollback triggers before production rollout.
- Tie alerts to actionable runbooks and clear ownership.
- Base SLO targets on observed baseline metrics.
Never:
- Deploy to production without staged verification.
- Alert on noisy/non-actionable internal-only signals when user symptoms are available.
- Skip health checks, post-deploy validation, or rollback capability.
Reference Materials
reference/deployment-strategies.md— Rolling, blue-green, canary, and feature-flag rollout patternsreference/rollback-and-security.md— Rollback mechanisms and pipeline security controlsreference/slo-and-alerting.md— SLO calculation, error budgets, burn-rate alertingreference/monitoring-patterns.md— Metric types, distributed tracing, log aggregation, dashboard design Containerization:- Docker — Dockerfiles, multi-stage builds, Compose, image hardening, BuildKit, container networking
Deployment Platforms:
- Railway — Nixpacks auto-build PaaS, managed Postgres/Redis, per-environment deploys, usage-based pricing
- Vercel — Edge-first frontend hosting, serverless functions, preview deployments, Next.js-native platform
- Netlify — Jamstack hosting, Edge Functions, built-in form handling, framework-agnostic deploys
- Render — Managed web services, background workers, cron jobs, auto-scaling, private networking
- Coolify — Self-hosted PaaS alternative, deploy to own servers, 280+ one-click services, no vendor lock-in
What ships with it
4 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.
- 2mo ago First seen · 86 lines · 45 tokens per session scan A 5e77cc1484a3
platform-operations is a skill published in the GitHub repository rsmdt/the-startup (575 stars, last pushed 3d ago), licensed MIT. It adds 45 tokens to every session and 924 once invoked, about $0.0002 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-30.
Other skills, from other repositories
watch-patterns
Correct watcher construction for long-running operations. TRIGGER when: watching a long-running operation (CI, deploy, log stream), writing poll/until loops, or using the Monitor tool. SKIP: production alerts/metrics (use monitoring-observability); log formatting (use logging-standards); diagnosing the bug (use…
vibe-ship
Generates and audits production-ready deployment setups for any app. Detects the stack from the repo (Node/Next.js/Bun/Deno, Python/Django/FastAPI, Go, Rust, Java/Spring, .NET, Ruby/Rails, PHP/Laravel, Elixir/Phoenix, static sites, monorepos) and writes hardened Dockerfiles, .dockerignore, compose.yaml with…
ci-cd
Use when setting up or modifying CI/CD pipelines, quality gates, test runners, or deployment pipeline configuration through workflow files. Not for triggering a deployment.
repo-health-triage
Use when a scheduled or watcher tick requests a repository-health pass. Not for source, label, merge, or close mutation.
loop-on-ci
Monitor PR checks and fix failures until green. Uses gh pr checks as the source of truth for PR-attached checks.
ci-workflow
Design and maintain .NET CI workflows for F#, C#, and mixed solutions with SDK setup, restore, build, test, format checks, package checks, caching, and matrix decisions.