Update Aegis

CommunityPopular

GanyuanRan

update-aegis

Use when the user says `aegis:update`, asks to update or upgrade an installed Aegis method-pack, wants the latest Aegis version, or asks whether Aegis is current on this host.

Overview

Publisher	GanyuanRan
Repository	`Aegis`
Skill name	`update-aegis`
Stars	1.2K
Forks	52
Bundled files	Instructions only
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by GanyuanRan on GitHub. Read the source before you install it.

Installation

Install the Update Aegis AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/GanyuanRan/Aegis.git /tmp/Aegis
mkdir -p .claude/skills
cp -r /tmp/Aegis/skills/update-aegis .claude/skills/update-aegis

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Update Aegis in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Update Aegis on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Update Aegis is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Update Aegis

Update the installed Aegis Method Pack for the current AI coding host.

This skill is host maintenance. Do not edit the target project just because the user asked to update Aegis.

Default Semantics

aegis:update updates the current host's registered Aegis installation.
Updating every registered host requires an explicit --all request.
If more than one host is registered and the current host cannot be identified, ask one concrete question before updating.
Do not update a development checkout when the installed method-pack root is a separate path.
Do not perform background automatic updates. The local registry may record updateMode, but this skill only performs explicit user-triggered updates.

Evidence First

From the installed method-pack root, inspect the host-scoped registry:

bash
python scripts/aegis-update.py status --json

If the registry is missing, register the current host before updating. Use the host's install guide and actual discovery path rather than guessing.

If ~/.config/aegis/config.toml already declares method_pack_root, prefer that canonical root when registering additional hosts. Host-specific discovery paths, copied skill directories, plugin caches, or adapter payloads should be treated as generated / host-managed views into the same Aegis body, not as separate editable checkouts.

Codex example:

bash
python scripts/aegis-update.py register \
  --host codex \
  --sync-mode junction \
  --discovery-root ~/.agents/skills/aegis \
  --reload-hint "restart Codex"

Copy-based host example:

bash
python scripts/aegis-update.py register \
  --host codebuddy \
  --sync-mode copy-skills \
  --discovery-root ~/.codebuddy/skills \
  --reload-hint "restart CodeBuddy"

Prefixed direct-child host example:

bash
python scripts/aegis-update.py register \
  --host copilot \
  --sync-mode junction \
  --discovery-shape direct-child \
  --discovery-root <target-repo>/.github/skills \
  --discovery-name-prefix aegis- \
  --reload-hint "restart Copilot session or reopen the repository"

Kimi Code CLI automatic installations are plugin-managed. Do not use the Aegis updater against Kimi's managed plugin copy. In Kimi, run the native update or reinstall flow, verify the selected managed plugin, then reload:

text
/plugins install https://github.com/GanyuanRan/Aegis
/plugins info aegis
/reload

If Kimi requires confirmation or removal before replacing the managed copy, follow its exact plugin-manager prompt. Then locate the managed root from /plugins info aegis and run:

bash
cd <aegis-method-pack-root>
python scripts/aegis-doctor.py --json --host-profile kimi-code-auto

Kimi Code CLI Explicit Compatibility Installation example:

bash
python scripts/aegis-update.py register \
  --host kimi-code \
  --sync-mode junction \
  --reload-hint "restart Kimi Code CLI"

When --discovery-root is omitted for kimi, kimi-code, or kimi-code-cli, the updater uses $KIMI_CODE_HOME/skills or, when KIMI_CODE_HOME is unset, ~/.kimi-code/skills. Use this updater path only when the Aegis Kimi plugin is disabled or uninstalled and the user has selected explicit compatibility mode.

Plugin-managed hosts can be registered, but the updater reports that the host plugin manager owns the update path:

bash
python scripts/aegis-update.py register \
  --host opencode \
  --sync-mode plugin-managed \
  --reload-hint "restart OpenCode"

Update Commands

Current or explicitly selected host:

bash
python scripts/aegis-update.py update --host <host> --json

All registered hosts, only when the user explicitly asks for all-host update:

bash
python scripts/aegis-update.py update --all --json

Preview without touching files:

bash
python scripts/aegis-update.py update --host <host> --dry-run --json

If the installed checkout has local changes, do not overwrite them. Either ask the user how to proceed or, with explicit permission, preserve them with:

bash
python scripts/aegis-update.py update --host <host> --stash --json

Completion Evidence

Treat the update as complete only when the updater reports the selected host and the post-update doctor verification succeeds. For link-based discovery roots (junction, symlink, or repo-only), the updater passes discoveryRoot through to aegis-doctor.py --discovery-root; when a registered direct-child view declares discoveryNamePrefix, the updater also passes --discovery-name-prefix. For copy-based hosts, it verifies that copied Aegis skill directories exist after the copy step, then runs doctor against the method-pack root.

When multiple registered hosts share the same methodPackRoot, the updater now reuses a single method-pack checkout update and then refreshes each host's exposure or verification path separately.

Report:

selected host / installation id
previous and final commit when available
whether the install was updated or already current
sync mode used
doctor verification result
restart or reload hint

If the updater skips a plugin-managed host, state that the host plugin manager owns the update path and give the reload or reinstall hint.

For Kimi automatic installations, completion also requires /plugins info aegis, /reload or /new, the kimi-code-auto doctor profile, and the host-native automatic-entry checks from docs/README.kimi-code.md. File discovery or a generic doctor result alone is not sufficient.

Frequently asked questions

What does the Update Aegis AI skill do?

Use when the user says `aegis:update`, asks to update or upgrade an installed Aegis method-pack, wants the latest Aegis version, or asks whether Aegis is current on this host.

Why use Update Aegis on TypingMind?

Because you install it once and use it with any model. Update Aegis is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Update Aegis in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/GanyuanRan/Aegis/tree/main/skills/update-aegis. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Update Aegis?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Update Aegis?

As many as you like. As long as a model supports skills, you can use Update Aegis with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Update Aegis AI skill free?

Yes. It is published on GitHub by GanyuanRan under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Using Git Worktrees

obra

CommunityPopular

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

Using Superpowers

Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

Verification Before Completion

obra

CommunityPopular

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence…

Writing Plans

Use when you have a spec or requirements for a multi-step task, before touching code

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Update Aegis

Default Semantics

Evidence First

Update Commands

Completion Evidence

Frequently asked questions

Related AI Skills

Set up your own AI workspace now