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/megamen32/lasthumancommit/claude-mdgit clone --depth 1 https://github.com/megamen32/LastHumanCommitWhat 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.02522 | $0.02522 |
| Opus 5 | $0.01261 | $0.01261 |
| Sonnet 5 | $0.00504 | $0.00504 |
| Haiku 4.5 | $0.00252 | $0.00252 |
Grade A, and why
LastHumanCommit 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 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.
This is a copy
100% identical to LastHumanCommit AGENTS.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent role router
Workspace first
Before task work, inspect the repository root, git worktree list --porcelain,
the current branch or detached HEAD, and the default branch when identifiable.
Routine work stays in the current primary checkout. Do not create, switch, merge, or delete a branch or worktree for isolation, cleanliness, review, or an ordinary task. If the harness started in an auxiliary worktree, detached HEAD, or a non-default branch, the first user-visible update must warn the user and show the exact worktree path, branch, and primary checkout.
If the user explicitly asks LHC to create a worktree, create it only at
<primary-project-root>/.worktrees/<task-slug>. Never create a project worktree
in /tmp, a home cache, a sibling directory, or harness-owned storage. If the
harness already selected another checkout, do not create a second one or move
silently. Follow src/common/protocols/SHARED_WORKTREE.md for concurrent edits.
Project-local temporary storage
All temporary project material lives under <project-root>/.tmp/, which the
project must ignore in Git. This includes source code, repository clones and
exports, build trees and caches, binaries, packages, APK/DMG files, archives,
checksums, and release artifacts, even when they exist only briefly. Never put
such material in system /tmp, $TMPDIR, or a language runtime's default temp
directory. System temp is allowed only for tiny non-code OS primitives when an
OS or API genuinely requires it, never for project data or deliverables.
Resolve one role
If an enclosing instruction explicitly assigns one of these roles, read only that role file and follow it:
- Lead:
src/common/agents/Lead.md - Overseer:
src/common/agents/Overseer.md - Worker:
src/common/agents/Worker.md - Tester:
src/common/agents/Tester.md - Reviewer:
src/common/agents/Reviewer.md
Do not read unrelated role prompts. If it says you are a subagent but assigns no
known role, stop and ask L; never promote yourself to Lead. Otherwise you are L:
read src/common/agents/Lead.md.
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 · 223 lines · 2,522 tokens per session scan A 317d75b8e73c
LastHumanCommit CLAUDE.md is an instructions file published in the GitHub repository megamen32/LastHumanCommit (2 stars, last pushed 2d ago), licensed MIT. It adds 2,522 tokens to every session, about $0.0126 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to LastHumanCommit AGENTS.md, differing in 0 lines, and is treated as a copy.
Other instructions, from other repositories
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.
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).
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.