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/altimateai/altimate-code/releasegit clone --depth 1 https://github.com/AltimateAI/altimate-codeWhat 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.00037 | $0.05490 |
| Opus 5 | $0.00018 | $0.02745 |
| Sonnet 5 | $0.00007 | $0.01098 |
| Haiku 4.5 | $0.00004 | $0.00549 |
Grade A, and why
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 yesterday.
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 — 443 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release altimate-code
Automate the complete release process. The core principle: find and fix everything before tagging. No follow-up PRs.
Input
$ARGUMENTS = version bump type: patch (default), minor, or major. Can also be an explicit version like 0.6.0.
Step 0: Read the Release Guide
Read the official release documentation and current changelog style:
cat docs/RELEASING.md
head -80 CHANGELOG.md
Cross-check RELEASING.md against this skill. If it has new steps or prerequisites, warn the user and adapt.
Step 1: Determine Version
npm info @altimateai/altimate-code version
patchor empty: bump patch (e.g.,0.5.17→0.5.18)minor: bump minor (e.g.,0.5.17→0.6.0)major: bump major (e.g.,0.5.17→1.0.0)- Explicit version (matches
\d+\.\d+\.\d+): use directly
Confirm with user: "Releasing v{NEXT_VERSION} (current: v{CURRENT_VERSION}). Proceed?"
Step 2: Deterministic Preflight
Run the preflight script — it is the gate, not a suggestion:
bun script/release-preflight.ts --version {NEXT_VERSION} --stage pre
It verifies, fail-closed:
- clean worktree (untracked files are only a warning — they must NOT be staged later)
- HEAD equals freshly fetched
origin/main— this is the invariant, not "on branch main". Releasing from a worktree or a branch whose HEAD equalsorigin/mainis fine; push viaHEAD:main. If HEAD diverges, STOP. - no local or remote tag
v{NEXT_VERSION}already exists (stale fork-inherited tags nearly shipped a wrong artifact in v0.9.1) - version is valid SemVer, greater than npm
latest, not already published - every prerelease tag on the target line (
v{X.Y}.*-*) is an ancestor oforigin/main - no open PRs labeled
release-blocker - which previous tag the auto-generated release notes will compare against (sanity-check it: for v0.9.1 the old logic would have diffed against a stray divergent tag and omitted a 165-commit merge)
- marker guard clean
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.
- yesterday First seen · 443 lines · 37 tokens per session scan A 3d2dc29a9d8d
release is a command published in the GitHub repository AltimateAI/altimate-code (803 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 5,490 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-30.
Other commands, from other repositories
MIGRATE_DESIGN
Design doc for the migration tool PR. Author: Sol ([email protected]). Co-authored-by: wakesync.
awesome-chatgpt
Search awesome-ChatGPT-repositories for open-source GitHub repositories related to ChatGPT and LLMs.
agentlas-cloud
Staff a task only from the signed-in owner's Agent Cloud agents.
review-epo-claims
Analyze patent claims for EPO Art. 84 EPC compliance - clarity, conciseness, support by description.
commit
智能生成 Git 提交信息并提交.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.