Borrowing it
Nothing to install: this file belongs to singula-ai/alego. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/singula-ai/alego/main/.agents/skills/alego-create-upgrade-guide/SKILL.mdgit clone --depth 1 https://github.com/singula-ai/alegoWrote 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/singula-ai/alego/alego-create-upgrade-guide)<a href="https://agentmods.dev/skills/singula-ai/alego/alego-create-upgrade-guide"><img src="https://agentmods.dev/badge/skills/singula-ai/alego/alego-create-upgrade-guide/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/singula-ai/alego/alego-create-upgrade-guide"><img src="https://agentmods.dev/badge/skills/singula-ai/alego/alego-create-upgrade-guide.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.00076 | $0.00853 |
| Opus 5.5 | $0.00030 | $0.00341 |
| Sonnet 5.5 | $0.00015 | $0.00171 |
| Haiku 4.5 | $0.00008 | $0.00085 |
Grade A, and why
alego-create-upgrade-guide 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 6d 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.
This is a copy
92% identical to dsh-create-upgrade-guide — 14 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ALEGO Create Upgrade Guide
An upgrade guide tells a reader who runs release vT what to change to run the next release. Write it in the change that introduces the break, as soon as the break is recognized; do not defer it to release preparation.
Scope
Write a guide only for breaks that someone outside the repository can observe after upgrading:
alegocommands, flags, and profile names;cordis.yml, patch, overlay, and settings keys or their accepted values;- persisted user data: Session logs, SQLite stores, and user data directories;
- TypeScript and Python SDK exports, JSON-RPC, HTTP, and ACP messages;
- published package names and entry points.
Pre-stable internal APIs whose consumers are all updated in the same change need no guide. A Session-format change still follows type acknowledgements; its guide states only the reader's actions and links that record.
Location
docs/upgrade-guide/v<version>/<item>/guide.md
<version>is theversionfield of the rootpackage.jsonwhen you write the guide, for examplev0.1.7-rc.2. The guide describes the upgrade from that release to the next one.<item>is a kebab-case name of the changed surface, for exampleprofile-flag-rename.- Each item directory holds exactly
guide.md, its Chinese counterpartguide.zh.md, and the pairing recordguide.i18n.yaml: no index, no attachments.
Maintenance
While the root version is unchanged, the current version directory describes the delta from vT to current master. When a later change touches a surface a guide there covers, update that guide in the same change; delete the guide when the break is reverted. After the version bump, guides in older version directories are frozen; a new break goes into the new version directory. Never write a guide spanning more than one release.
Format
Start from the upgrade-guide template. verify-upgrade-guides enforces:
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.
- 6d ago First seen · 55 lines · 76 tokens per session scan A 071178e642d6
alego-create-upgrade-guide is a skill published in the GitHub repository singula-ai/alego (109 stars, last pushed 3d ago), licensed MIT. It adds 76 tokens to every session and 853 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to dsh-create-upgrade-guide, differing in 14 lines, and is treated as a copy.
Other skills, from other repositories
ctx
Codebase intelligence and evidence-driven governance with the indexed ctx CLI. Use when exploring an unfamiliar repository, locating symbols or callers, checking for existing implementations, estimating change impact, enforcing architecture rules, scoring a branch, finding hotspots or duplication, or analyzing…
ctx
Codebase intelligence and evidence-driven governance with the indexed ctx CLI. Use when exploring an unfamiliar repository, locating symbols or callers, checking for existing implementations, estimating change impact, enforcing architecture rules, scoring a branch, finding hotspots or duplication, or analyzing…
managing-mcp-servers
Use when the user asks to add, change, remove, enable or disable an MCP server, or when an MCP tool is missing, needs sign-in, fails, or was blocked. ThinkRail runs pi in-process, so there is no pi command to call.
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.
agent-harness-testing
A testing method for coding tasks in unfamiliar projects. It first discovers how the project is tested, then uses a failing check followed by a passing check to verify a change.
todos
Use when the user asks for a shared plan, a task needs at least three substantive execution steps, or a loose TODO is pending. Without an explicit plan request, not for one-shot answers or checks, or one- to two-step work that is not already in the list.