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 event4u-app/agent-config --skill launch-readinessgit clone --depth 1 https://github.com/event4u-app/agent-configWrote 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/event4u-app/agent-config/launch-readiness)<a href="https://agentmods.dev/skills/event4u-app/agent-config/launch-readiness"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/launch-readiness/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/event4u-app/agent-config/launch-readiness"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/launch-readiness.svg" alt="Reviewed on agentmods" width="80" 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.00046 | $0.02323 |
| Opus 5 | $0.00023 | $0.01162 |
| Sonnet 5 | $0.00009 | $0.00465 |
| Haiku 4.5 | $0.00005 | $0.00232 |
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 8d 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
launch-readiness
When to use
- A change is about to merge that crosses a release boundary (new feature on
main, version bump, public-facing comms attached). - An ops handoff is implied — the on-call rotation, support team, or downstream consumers need to know.
- A rollback criterion has not been written down yet.
Do NOT use for routine internal merges
(finishing-a-development-branch)
or for the comms text itself (release-comms).
This skill produces the decision to ship and the rollback contract.
Cognition cluster
- Mental model 10 — Reversible vs irreversible. Map every step
of the rollout to a reversibility class; the rollback criteria
must name the irreversible steps and the abort threshold for each.
See
docs/contracts/mental-models.md§ 10. - Mental model 29 — Pre-mortems. Imagine the rollout failed in
six hours; what failed first? The pre-mortem becomes the rollback
criteria, not a separate document. See
mental-models.md§ 29. - Mental model 4 — Second-order thinking. Enumerate what
becomes harder after the launch (rollback cost, contributor
ergonomics, doc churn). See
mental-models.md§ 4. - Team + product context-spine slots. Read team for the
on-call rotation and ops handoff path; read product for the
segment / cohort exposure of the rollout. See
context-spine.
Procedure
1. Identify the launch shape
One sentence: "This change ships X to segment Y behind
rollout mechanism Z." If you cannot, the change is not
release-shaped; route to finishing-a-development-branch.
2. Inspect the pre-merge checklist
Walk the diff with the following gates:
- Tests green on the integration suite (cite the run).
- Quality gates green (static analysis / linters / type-checks).
- Migrations are reversible OR the irreversibility is explicit.
- Feature flag / kill switch named, default off unless intended.
- Doc / changelog / release notes present (hand off to
release-commsfor the prose). - Rollback path tested at least mentally; named in step 4.
What ships with it
1 file 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.
- 8d ago First seen · 221 lines · 46 tokens per session scan A 67eb810c5d05
launch-readiness is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 2,323 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-09-04.
Other skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
finishing-a-development-branch
A process for finishing a completed development branch. A branch is a separate line of code changes that can later be merged or submitted as a pull request.
skillshare-changelog
Generate CHANGELOG.md entry from recent commits in conventional format. Also syncs the website changelog page. Use this skill whenever the user asks to: generate a changelog, document what changed between tags, or create a new CHANGELOG entry. If you see requests like "write the changelog for v0.17", "what changed…
github-release-briefing-skill
Create a source-linked briefing for the latest published GitHub release of a public repository. Use for engineering teams tracking a dependency release; do not use it to publish releases or change repositories.
devops/changelog-generation
A method for creating a CHANGELOG, a document that records what changed in each software release. It reads Git commit history and release-pipeline reports, then groups changes using common commit and changelog conventions.
get-unpublished-changes
Compare HEAD with the latest published npm versions and list all unpublished changes by release layer. Triggers: unpublished changes, changelog, what changed, whats new.