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 commands/sifxprime/kodelyth-ecc/pre-releasegit clone --depth 1 https://github.com/sifxprime/kodelyth-eccWrote 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/commands/sifxprime/kodelyth-ecc/pre-release)<a href="https://agentmods.dev/commands/sifxprime/kodelyth-ecc/pre-release"><img src="https://agentmods.dev/badge/commands/sifxprime/kodelyth-ecc/pre-release.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.00030 | $0.00517 |
| Opus 5 | $0.00015 | $0.00259 |
| Sonnet 5 | $0.00006 | $0.00103 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
pre-release 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 2d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pre-release — Parallel Release Readiness Check
Three agents verify your release is safe to ship. Catches the things that turn a Friday deploy into a weekend incident.
What Gets Launched in Parallel
| Agent | Focus |
|---|---|
release-captain |
Semver correctness, changelog complete, rollback plan, smoke test coverage |
security-reviewer |
Last-minute security gaps, secrets, auth issues before code goes live |
code-reviewer |
Critical quality issues, dead code, regressions introduced in this release |
Usage
/pre-release # check current branch vs main
/pre-release v2.1.0 # check specific version tag
/pre-release --hotfix # fast-track: release-captain only, skip style issues
Report Format
## PRE-RELEASE REPORT
### Release Readiness (release-captain)
SEMVER: [correct / incorrect]
CHANGELOG: [complete / missing entries]
ROLLBACK: [plan exists / missing]
SMOKE: [covered / gaps]
### Security Clearance (security-reviewer)
CRITICAL: [list — block if any]
HIGH: [list]
### Code Quality (code-reviewer)
CRITICAL: [list — block if any]
HIGH: [list]
---
VERDICT: SHIP / FIX CRITICAL FIRST / BLOCK
When to Use
- Before cutting any release tag
- Before merging a large feature branch
- Before a hotfix deploy under pressure
- As the final gate before
npm publishor production push
Execute Now
Invoking this command is confirmation to proceed. Execute immediately:
- Determine target from
$ARGUMENTS(version tag, branch, or current state). - Spawn all agents simultaneously with
run_in_background: true:release-captain— release ritual check: semver, changelog, rollbacksecurity-reviewer— security clearance scancode-reviewer— final quality gate
- Wait for all to complete.
- Aggregate into the Pre-Release Report format above with a clear SHIP / BLOCK verdict.
- End with: "Ready to proceed with the release?" or list what must be fixed first.
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.
- 2d ago First seen · 67 lines · 30 tokens per session scan A 47c6e276b6de
pre-release is a command published in the GitHub repository sifxprime/kodelyth-ecc (11 stars, last pushed 3d ago), licensed MIT. It adds 30 tokens to every session and 517 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-03.
Other commands, from other repositories
ship
Run the pre-launch checklist via parallel fan-out to specialist personas, then synthesize a go/no-go decision.
hatch3r-release
Release-workflow orchestrator — preflight, SemVer bump, changelog sync, build + CycloneDX SBOM, adapter-output verification, quality gates, release-notes reconciliation, then stop before publish/merge for human approval.
ship
通过并行 fan-out 到 specialist personas 运行发布前 checklist，然后综合 go/no-go decision.
complete-milestone
Archive a completed milestone, generate a release report, and prepare the next.
sdk-release
You are an autonomous engineer for the cashfree/agent-skills repository. An issue labelled sdk-release reports that a new version of a Cashfree SDK or REST API has shipped. Your job: research the release from authoritative sources, update the changelog knowledge-base skill (and any integration skill the change…
ship
Run the pre-launch checklist via parallel fan-out to specialist personas, then synthesize a go/no-go decision.