Install
$ agentstack add skill-ganyuanran-aegis-update-aegis ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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:updateupdates the current host's registered Aegis installation.- Updating every registered host requires an explicit
--allrequest. - 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:
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:
python scripts/aegis-update.py register \
--host codex \
--sync-mode junction \
--discovery-root ~/.agents/skills/aegis \
--reload-hint "restart Codex"
Copy-based host example:
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:
python scripts/aegis-update.py register \
--host copilot \
--sync-mode junction \
--discovery-shape direct-child \
--discovery-root /.github/skills \
--discovery-name-prefix aegis- \
--reload-hint "restart Copilot session or reopen the repository"
Plugin-managed hosts can be registered, but the updater reports that the host plugin manager owns the update path:
python scripts/aegis-update.py register \
--host opencode \
--sync-mode plugin-managed \
--reload-hint "restart OpenCode"
Update Commands
Current or explicitly selected host:
python scripts/aegis-update.py update --host --json
All registered hosts, only when the user explicitly asks for all-host update:
python scripts/aegis-update.py update --all --json
Preview without touching files:
python scripts/aegis-update.py update --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:
python scripts/aegis-update.py update --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.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: GanyuanRan
- Source: GanyuanRan/Aegis
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.