Borrowing it
Nothing to install: this file belongs to mihaipora/zorya. 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/mihaipora/zorya/main/.claude/skills/update/SKILL.mdgit clone --depth 1 https://github.com/mihaipora/zoryaWrote 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/mihaipora/zorya/update)<a href="https://agentmods.dev/skills/mihaipora/zorya/update"><img src="https://agentmods.dev/badge/skills/mihaipora/zorya/update/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/mihaipora/zorya/update"><img src="https://agentmods.dev/badge/skills/mihaipora/zorya/update.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.00045 | $0.01475 |
| Opus 5.5 | $0.00018 | $0.00590 |
| Sonnet 5.5 | $0.00009 | $0.00295 |
| Haiku 4.5 | $0.00005 | $0.00147 |
Grade C, and why
update scanned grade C with 1 finding 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 1mo 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
If cancelled, clean up the temp dir (`rm -rf <TEMP_DIR>`) and stop. Copies of this mod
1 near-identical copy found in the catalogue:
- update — 95% identical, 10 lines differ
How it starts
The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update NanoClaw
Pull upstream changes and merge them with the user's installation, preserving skills and customizations. Scripts live in .claude/skills/update/scripts/.
Principle: Handle everything automatically. Only pause for user confirmation before applying changes, or when merge conflicts need human judgment.
UX Note: Use AskUserQuestion for all user-facing questions.
1. Pre-flight
Check that the skills system is initialized:
test -d .nanoclaw && echo "INITIALIZED" || echo "NOT_INITIALIZED"
If NOT_INITIALIZED: Run initSkillsSystem() first:
npx tsx -e "import { initNanoclawDir } from './skills-engine/init.js'; initNanoclawDir();"
Check for uncommitted git changes:
git status --porcelain
If there are uncommitted changes: Warn the user: "You have uncommitted changes. It's recommended to commit or stash them before updating. Continue anyway?" Use AskUserQuestion with options: "Continue anyway", "Abort (I'll commit first)". If they abort, stop here.
2. Fetch upstream
Run the fetch script:
./.claude/skills/update/scripts/fetch-upstream.sh
Parse the structured status block between <<< STATUS and STATUS >>> markers. Extract:
TEMP_DIR— path to extracted upstream filesREMOTE— which git remote was usedCURRENT_VERSION— version from localpackage.jsonNEW_VERSION— version from upstreampackage.jsonSTATUS— "success" or "error"
If STATUS=error: Show the error output and stop.
If CURRENT_VERSION equals NEW_VERSION: Tell the user they're already up to date. Ask if they want to force the update anyway (there may be non-version-bumped changes). If no, clean up the temp dir and stop.
3. Preview
Run the preview to show what will change:
npx tsx scripts/update-core.ts --json --preview-only <TEMP_DIR>
This outputs JSON with: currentVersion, newVersion, filesChanged, filesDeleted, conflictRisk, customPatchesAtRisk.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 172 lines · 45 tokens per session scan C dbf8e9eded04
update is a skill published in the GitHub repository mihaipora/zorya (5 stars, last pushed 7mo ago), licensed MIT. It adds 45 tokens to every session and 1,475 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.