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/release-readinessnpx skills add evolplus/talos --skill release-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/release-readiness)<a href="https://agentmods.dev/skills/evolplus/talos/release-readiness"><img src="https://agentmods.dev/badge/skills/evolplus/talos/release-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.00054 | $0.00660 |
| Opus 5 | $0.00027 | $0.00330 |
| Sonnet 5 | $0.00011 | $0.00132 |
| Haiku 4.5 | $0.00005 | $0.00066 |
Grade A, and why
release-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 3d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Readiness
When to use
Use this skill before any shared-environment deployment, release candidate promotion, or production change proposal. The goal is not to deploy; it is to decide whether deployment is safe to attempt.
Inputs and outputs
- Inputs: task ID, release candidate identifier, linked implementation tasks, QA reports, deploy reports, architecture/SRS constraints, migration notes, rollback plan, config contract, and approval evidence.
- Outputs: readiness verdict, blocking findings, required follow-up tasks, and
docs/devops/<task-id>/release-readiness.mdor equivalent report content.
Procedure
- Identify the release candidate. Record commit SHA, image tag/digest, package version, migration version, and build provenance. Reject mutable identifiers unless explicitly approved.
- Verify functional evidence. Confirm required QA reports pass, staging/local deploy reports exist, and smoke/e2e coverage matches the task risk.
- Check dependency and security posture. Review dependency audit/security findings, external integration adequacy, data handling, and any open security/compliance issues.
- Run operational gates. Consult
migration-safety,rollback-readiness,secrets-config-audit, andobservability-readinesswhen applicable. - Review environment compatibility. Verify runtime config keys, platform/architecture constraints, database versions, queue/cache dependencies, feature flags, and external endpoints.
- Confirm approvals. Staging needs task-level approval. Production needs human change approval and rollback ownership.
- Emit a verdict. Use
ready,ready-with-warnings, orblocked. A warning must be non-critical and have an owner; a blocker prevents deployment.
Hard rules
- Never treat source code existence as release readiness; require runtime/test evidence.
- Never approve a release candidate with unresolved migration, rollback, secret/config, or observability blockers.
- Never hide warnings in prose; list each warning with owner, impact, and expiration.
- Never expose secrets while checking config readiness.
- Never deploy from this skill; route to the appropriate deployment skill after a
readyverdict.
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.
- 3d ago First seen · 46 lines · 54 tokens per session scan A dba1c3a88602
release-readiness is a skill published in the GitHub repository evolplus/talos (8 stars, last pushed 29d ago), licensed Apache-2.0. It adds 54 tokens to every session and 660 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…