Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/xeeva/genesis/updatenpx skills add xeeva/Genesis --skill updategit clone --depth 1 https://github.com/xeeva/GenesisWhat 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 | $0.00037 | $0.00535 |
| Opus 5 | $0.00018 | $0.00267 |
| Sonnet 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 2d 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.
- 2d 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 5mo ago), licensed MIT. It adds 37 tokens to every session and 535 once invoked, about $0.0002 per session on Opus 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
knowledge-base
Create and maintain a Markdown knowledge base that any AI agent can read, search, and update. Use when the user wants to start a knowledge base, add or update notes, organize docs/notes for an agent or LLM to consume, build an index of notes, or run a cleanup/maintenance pass on an existing MD knowledge base. Triggers…
peer-review
Structured manuscript/grant review with checklist-based evaluation. Use when writing formal peer reviews with specific criteria methodology assessment, statistical validity, reporting standards compliance (CONSORT/STROBE), and constructive feedback. Best for actual review writing, manuscript revision. For evaluating…
scientific-critical-thinking
Evaluate scientific claims and evidence quality. Use for assessing experimental design validity, identifying biases and confounders, applying evidence grading frameworks (GRADE, Cochrane Risk of Bias), or teaching critical analysis. Best for understanding evidence quality, identifying flaws. For formal peer review…
statistical-analysis
Guided statistical analysis for research data - test selection, assumption checking, effect sizes, power analysis, Bayesian alternatives, and APA-formatted reporting. Use whenever a user wants to compare groups, test a hypothesis, analyze experimental or survey data, check statistical assumptions, compute required…
statistical-power
Sample-size and statistical power calculations for planning studies. Use whenever someone asks "how many subjects/samples/replicates do I need", wants an a priori power analysis, a minimum detectable effect (MDE), a power curve, or needs to justify a sample size for a grant, IRB protocol, or pre-registration. Covers…
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…