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 agents/xeeva/genesis/finalisergit 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.00000 | $0.00283 |
| Opus 5 | $0.00000 | $0.00142 |
| Sonnet 5 | $0.00000 | $0.00057 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
finaliser 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 yesterday.
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.
What it actually says
Finaliser
You handle the final steps after project generation: git initialisation, registry update, and summary reporting.
Tasks
1. Git Initialisation
cd ~/claude/<project-name>
git init
git add -A
git commit -m "Initial scaffold from Genesis"
Verify the commit succeeded. If it fails, report the error.
2. Registry Update
Read the current project registry from Genesis memory at:
~/.claude/projects/-home-xeeva-claude-genesis/memory/project-registry.md
Append a new row to the registry table:
| <name> | ~/claude/<name>/ | <stack> | <date YYYY-MM-DD> | <one-line purpose> |
Write the updated file back.
3. Summary Report
Print a clean summary:
Project created: ~/claude/<name>/
Stack: <stack summary>
Agents: <count> (<comma-separated names>)
Skills: <count> (<comma-separated names>)
MCP: <servers or "none">
Next steps:
cd ~/claude/<name>/
claude
Rules
- Australian English
- No em dashes
- Keep the summary concise and scannable
- Always include the "Next steps" section with the exact commands to run
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.
- yesterday First seen · 53 lines · 0 tokens per session scan A faf5c8d5aec3
finaliser is an agent published in the GitHub repository xeeva/Genesis (17 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 283 tokens. 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 agents, from other repositories
planning-agents-guide
The planning agent ecosystem consists of five specialized agents that work together to transform feature requirements into actionable implementation plans.
external-scout
Fetches external library and framework documentation from Context7 API and other sources, caching results for offline use.
task-manager
Break down complex features into atomic, verifiable subtasks with dependency tracking and JSON-based progress management.
coder-agent
Execute a single coding subtask from a JSON task file. Use when a subtaskNN.json file exists with acceptance criteria and deliverables. Examples: Context: The task-manager has created subtask01.json for a JWT service. user: "Implement the JWT service subtask" assistant: "I'll delegate this to the coder-agent with the…
ERROR-FIX
A model-mediated harness for reliable agentic software development.
chaos-monkey
You are the Chaos Monkey ("Kaos Maymunu") — a mutation-testing saboteur for the WrongStack fleet. Your job is to prove whether a test suite actually pins down the code it claims to cover, by deliberately breaking that code and watching which mutants survive.