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 instructions/javanc/homunculus/claude-mdgit clone --depth 1 https://github.com/JavanC/HomunculusWrote 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/instructions/javanc/homunculus/claude-md)<a href="https://agentmods.dev/instructions/javanc/homunculus/claude-md"><img src="https://agentmods.dev/badge/instructions/javanc/homunculus/claude-md.svg" alt="Measured on agentmods" 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.00361 | $0.00361 |
| Opus 5 | $0.00180 | $0.00180 |
| Sonnet 5 | $0.00072 | $0.00072 |
| Haiku 4.5 | $0.00036 | $0.00036 |
Grade A, and why
Homunculus CLAUDE.md 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 5d 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.
What it actually says
Homunculus — Development Guide
Release Checklist
Every change to this repo must complete these steps in order:
- Code changes — implement the feature/fix
- README.md — update What's New section + any affected docs
- i18n sync — update
docs/zh-TW/README.mdanddocs/zh-CN/README.mdto match - package.json — bump version (semver: patch/minor/major)
- git commit + push — descriptive commit message
- npm publish —
npm publishfrom repo root - GitHub release —
gh release create vX.Y.Zwith release notes - assistant plan.md — sync
~/assistant/projects/homunculus/plan.mdif applicable
Project Structure
bin/— CLI entry points (init, upgrade, night)core/— Evolution scripts copied to user projects during initcommands/— Slash commands copied to.claude/commands/during inittemplates/— CLAUDE.md, architecture.yaml, rules templates for initdocs/— Long-form documentationexamples/reference/— Real-world reference implementation from the author's system
Key Design Decisions
- Zero dependencies — Only Node.js stdlib + Claude CLI
- File copy, not symlink — init copies files so users can customize freely
- Manifest-based upgrade —
.manifest.jsontracks SHA256 hashes for diff-aware upgrades - Never touch user content — upgrade never modifies CLAUDE.md, architecture.yaml, instincts, skills
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.
- 5d ago First seen · 31 lines · 361 tokens per session scan A 3d9f4218400e
Homunculus CLAUDE.md is an instructions file published in the GitHub repository JavanC/Homunculus (15 stars, last pushed 3mo ago), licensed MIT. It adds 361 tokens to every session, about $0.0018 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).