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/validatenpx skills add xeeva/Genesis --skill validategit 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.00032 | $0.00590 |
| Opus 5 | $0.00016 | $0.00295 |
| Sonnet 5 | $0.00006 | $0.00118 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
validate 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Validator
Check that a target project directory has all expected Claude Code infrastructure files and that they are well-formed.
Usage
The user provides a project name or path. Default to the most recently created project if none specified.
Checks
Required Files
-
CLAUDE.mdexists and is non-empty -
.claude/settings.jsonexists and is valid JSON -
.claude/agents/directory has at least 3 agent files (test-runner, code-reviewer, doc-writer) -
.claude/skills/directory has at least 4 skill directories (test, lint, review, commit) - Each skill directory contains a
SKILL.mdwith valid YAML frontmatter -
docs/README.mdexists -
docs/architecture.mdexists -
.gitignoreexists - Git repo is initialised (
.git/exists)
Memory Files
-
~/.claude/projects/-home-xeeva-claude-<name>/memory/MEMORY.mdexists -
~/.claude/projects/-home-xeeva-claude-<name>/memory/user-profile.mdexists -
~/.claude/projects/-home-xeeva-claude-<name>/memory/project-context.mdexists
Content Quality
- CLAUDE.md contains "Australian English" rule
- CLAUDE.md contains "em dash" rule
- CLAUDE.md contains "fail fast" or error handling section
- CLAUDE.md contains testing section
- settings.json has permissions.allow array
- settings.json has at least one hook
Optional Files
-
.mcp.jsonexists if integrations were specified (report if missing but expected) - Stack-specific config files exist (tsconfig.json, pyproject.toml, etc.)
Output
Report results as a checklist:
Validating: ~/claude/<name>/
Required Files: [12/12 passed]
Memory Files: [3/3 passed]
Content Quality: [5/6 passed]
- MISSING: settings.json has no hooks configured
Optional Files: [2/2 passed]
Overall: 22/23 checks passed
If all checks pass: "Project is fully configured and ready to use." If checks fail: list the failures with specific remediation steps.
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 · 64 lines · 32 tokens per session scan A f9e21be41e2b
validate is a skill published in the GitHub repository xeeva/Genesis (17 stars, last pushed 5mo ago), licensed MIT. It adds 32 tokens to every session and 590 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…