Borrowing it
Nothing to install: this file belongs to xeeva/Genesis. 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/xeeva/Genesis/main/.claude/skills/update/SKILL.mdgit clone --depth 1 https://github.com/xeeva/GenesisWrote 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/xeeva/genesis/update)<a href="https://agentmods.dev/skills/xeeva/genesis/update"><img src="https://agentmods.dev/badge/skills/xeeva/genesis/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/xeeva/genesis/update"><img src="https://agentmods.dev/badge/skills/xeeva/genesis/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.00037 | $0.00535 |
| Opus 5.5 | $0.00015 | $0.00214 |
| Sonnet 5.5 | $0.00007 | $0.00107 |
| Haiku 4.5 | $0.00004 | $0.00053 |
Grade A, and why
update 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Genesis
Check for and apply updates from the Genesis repository.
Steps
-
Verify location: Confirm you are operating in the Genesis directory (
~/claude/genesis/). If not, inform the user and exit. -
Check for local changes:
git -C ~/claude/genesis/ status --porcelain
If there are uncommitted changes, warn the user and ask whether to proceed (updates may conflict) or abort.
- Fetch updates:
git -C ~/claude/genesis/ fetch origin main
- Compare versions:
git -C ~/claude/genesis/ rev-list HEAD..origin/main --count
If the count is 0, report "Genesis is already up to date." and exit.
- Show what changed:
git -C ~/claude/genesis/ log HEAD..origin/main --oneline --no-decorate
Present the list of incoming changes to the user. Highlight notable updates (new agents, skills, templates, or stack support).
-
Confirm with the user: Ask whether to apply the updates. Use AskUserQuestion.
-
Apply updates:
git -C ~/claude/genesis/ pull origin main
- Report results: Summarise what was updated. If new skills or agents were added, mention them. If templates changed, note that future generated projects will use the updated templates.
What is Preserved
The following user-specific files are gitignored and will never be overwritten by updates:
personalisation.md-- your locale, output style, and profile preferencesenvironment.md-- your platform, shell, and path configuration.claude/settings.local.json-- local Claude Code permission overrides
The .example versions of these files (shipped with Genesis) may be updated to reflect new configuration options. After updating, check if the examples have new fields you might want to add to your own files.
Notes
- This skill only updates Genesis itself, not projects previously generated by Genesis.
- Previously generated projects are independent and unaffected by Genesis updates.
- If the pull fails due to conflicts, explain the situation and suggest
git stashor manual resolution.
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.
- 2mo ago First seen · 61 lines · 37 tokens per session scan A 8539962d4609
update is a skill published in the GitHub repository xeeva/Genesis (17 stars, last pushed 7mo ago), licensed MIT. It adds 37 tokens to every session and 535 once invoked, about $0.0001 per session on Opus 5.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 skills, from other repositories
version-bump
Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging, GitHub releases, and changelog generation. npm publishing is done by the tag-triggered GitHub Actions workflow through…
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
emerging-techniques-model-merging
Merge multiple fine-tuned models using mergekit to combine capabilities without retraining. Use when creating specialized models by blending domain-specific expertise (math + coding + chat), improving performance beyond single models, or experimenting rapidly with model variants. Covers SLERP, TIES-Merging, DARE, Task…
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.
release
Fully automate a release with version-bump and childhood.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.