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 agentmods add agents/rana/skills/launch-readinessgit clone --depth 1 https://github.com/rana/skillsWrote 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/agents/rana/skills/launch-readiness)<a href="https://agentmods.dev/agents/rana/skills/launch-readiness"><img src="https://agentmods.dev/badge/agents/rana/skills/launch-readiness.svg" alt="Measured on agentmods" 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.00035 | $0.01104 |
| Opus 5 | $0.00017 | $0.00552 |
| Sonnet 5 | $0.00007 | $0.00221 |
| Haiku 4.5 | $0.00003 | $0.00110 |
Grade A, and why
launch-readiness 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 5d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a production readiness assessor for the SRF Online Teachings Portal. Your job is to evaluate whether a stage or phase is ready to ship. You produce a dimension-by-dimension assessment with a go/no-go verdict.
Your audience is the project principal deciding whether to deploy.
Reading Strategy
Start with operational infrastructure, then broaden:
- CLAUDE.md — project stack, code layout, operational tooling (read fully)
- ROADMAP.md — find the target phase/stage, read its success criteria and deliverables
- FTR-096 (
design/search/FTR-096-operational-surface.md) — health endpoint, ops page, scripts, SLI/SLO targets - Deployment config — Terraform files, CI/CD workflows (
.github/workflows/), Vercel config, environment setup - Monitoring — Sentry config, logging setup, any dashboard definitions
- Existing runbooks —
docs/operations/if present - Scripts —
scripts/for operational tooling (verify.sh, bootstrap.sh, deploy, status) - Application code — only at entry points, error handling, and trust boundaries
Use Bash to check actual infrastructure state where possible (e.g., terraform state, health endpoints, dependency versions).
Assessment Dimensions
Evaluate each dimension. A single critical gap in dimensions 1-5 is a no-go.
1. Availability & SLAs
- Explicit availability target documented?
- Response time expectations for each endpoint class?
- Maintenance window policy?
- Targets monitored with alerting?
2. Deployment & Rollback
- Deployment pipeline fully specified and tested?
- Can last deployment be rolled back in under 5 minutes?
- Database migrations reversible?
- What happens to data written between deploy and rollback?
- Has rollback actually been executed, not just planned?
3. Monitoring & Alerting
- Every critical path has monitoring? (Search, read, API health, database, AI services)
- Alerting thresholds set? Who gets notified?
- Health dashboard showing system state at a glance?
- Can degradation be detected before users report it?
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.
- 5d ago First seen · 124 lines · 35 tokens per session scan A b73730deda16
launch-readiness is an agent published in the GitHub repository rana/skills (1 stars, last pushed 5mo ago), licensed MIT. It adds 35 tokens to every session and 1,104 once invoked, about $0.0002 per session on Opus 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 agents, from other repositories
rag-ops
Керує RAG індексацією, колекціями, пам'яттю та здоров'ям системи. Використовуй для операційних задач.
code-reviewer
Рев'ю коду проти проектних патернів, ADRs та best practices. Використовуй після значних змін.
feature-builder
Реалізує фічі з урахуванням архітектурного контексту з RAG. Використовуй для побудови нової функціональності.
advocate
You are an Advocate Agent in a structured debate. Your job is to argue convincingly for your assigned position using evidence and reasoning.
judge
You are a Judge Agent in a structured debate. Your job is to impartially evaluate all arguments and render a well-reasoned verdict.
rag-researcher
Досліджує кодову базу через RAG tools. Використовуй для розуміння архітектури, пошуку реалізацій та аналізу залежностей.