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 skills/evolplus/talos/observability-readinessnpx skills add evolplus/talos --skill observability-readinessgit clone --depth 1 https://github.com/evolplus/talosWrote 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/evolplus/talos/observability-readiness)<a href="https://agentmods.dev/skills/evolplus/talos/observability-readiness"><img src="https://agentmods.dev/badge/skills/evolplus/talos/observability-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 | $0.00061 | $0.00578 |
| Opus 5 | $0.00030 | $0.00289 |
| Sonnet 5 | $0.00012 | $0.00116 |
| Haiku 4.5 | $0.00006 | $0.00058 |
Grade A, and why
observability-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 4d 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Observability Readiness
When to use
Use this skill before staging/production deployment, before enabling traffic, and during release readiness for features whose failure needs operational detection.
Inputs and outputs
- Inputs: architecture/instrumentation contract, service list, health endpoints, expected logs/metrics/traces, dashboards/alerts, target environment, and incident runbook references.
- Outputs: observability readiness verdict, missing telemetry findings, dashboard/alert references, smoke probe evidence, and deploy-report observability fields.
Procedure
- Map critical signals. For each deployed service, identify health endpoint, readiness/liveness signal, key logs, metrics, traces, and business/user-impact indicators.
- Check deploy-time telemetry. Verify the new version emits startup logs, request logs, errors, latency, saturation/resource metrics, background job signals, and dependency health.
- Verify correlation. Confirm request IDs/correlation IDs connect frontend, backend, workers, and external calls where applicable.
- Confirm dashboards and alerts. Record dashboard names/links and alert names/status. Use names or URLs only; do not include tokens or private query credentials.
- Define smoke/synthetic probes. List post-deploy probes for user flows, API health, queues, scheduled jobs, and external integrations.
- Check runbook path. Ensure a human can move from alert to runbook to rollback/mitigation path.
- Emit verdict.
ready,ready-with-gaps, orblocked.
Hard rules
- Never promote a high-risk deployment with no health signal, no alert, and no rollback trigger.
- Never expose sensitive logs, PII, auth headers, trace baggage, API keys, or dashboard tokens.
- Never treat "container running" as observability readiness.
- Never invent SLOs or alert thresholds; record missing contracts as follow-up work.
- Never mark observability ready when incident responders cannot identify service/version/environment from telemetry.
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.
- 4d ago First seen · 44 lines · 61 tokens per session scan A 2780424e080a
observability-readiness is a skill published in the GitHub repository evolplus/talos (8 stars, last pushed 29d ago), licensed Apache-2.0. It adds 61 tokens to every session and 578 once invoked, about $0.0003 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 skills, from other repositories
convex-add
Add a capability to the CURRENT Convex app — consults the served Convex capability catalog for always-current procedures (billing, crons, auth, agent, search, …); falls back to built-in hosting or @convex-dev component search. TRIGGER when the user runs /add, or asks to add hosting/publishing or any backend capability…
twitter-reader
Read Twitter/X for financial research using opencli (read-only). Use this skill whenever the user wants to read their Twitter feed, search for financial tweets, view bookmarks, look up user profiles, or gather market sentiment from Twitter/X. Triggers include: "check my feed", "search Twitter for", "show my…
chenhao-limit-up
Use when evaluating A-share limit-up (涨停板) setups through Chen Hao's sentiment and momentum lens: market emotion cycles, board strength, follow-through, and short-term aggressive momentum trading.
trading-risk-gate
Unified pre-trade safety gate: Ruin check (Law #1), ergodicity audit, and win-rate dominance validation. Absorbs: ergodicity-check, law-of-ruin, win-rate-dominance.
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
multi-expert-analyzer
针对通用问题进行多领域专家联合分析, 综合稿产生前必经 fact-checker 与 red-team 两道独立校验。适用场景: 用户提出跨领域或不确定领域的复杂问题, 需要从多个专家角度分别搜证并相互校验后综合成文, 例如该不该买房、该不该跳槽、是否进入某个赛道等。触发关键词: 多角度分析、专家分析、综合分析、多视角、跨领域分析、从不同角度看、深度分析。问题只属于单一明确领域时, 优先使用该领域的专门 skill, 例如纯财务用 finance-core-analysis、纯技术用 software-architect。输出 (全部 markdown 保存到当前项目 markdown/ 目录): (1) 每位专家的中间分析稿…