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 skills add 0x7067/claude-jev --skill entiregit clone --depth 1 https://github.com/0x7067/claude-jevWrote 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/skills/0x7067/claude-jev/entire)<a href="https://agentmods.dev/skills/0x7067/claude-jev/entire"><img src="https://agentmods.dev/badge/skills/0x7067/claude-jev/entire/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/0x7067/claude-jev/entire"><img src="https://agentmods.dev/badge/skills/0x7067/claude-jev/entire.svg" alt="Reviewed on agentmods" width="80" 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.00037 | $0.00159 |
| Opus 5.5 | $0.00015 | $0.00064 |
| Sonnet 5.5 | $0.00007 | $0.00032 |
| Haiku 4.5 | $0.00004 | $0.00016 |
Grade A, and why
entire 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 26d 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
Entire's CLI is the source of truth for its own usage. Do not guess flags or subcommands.
Run entire agent-help for a map of when to use entire and which subcommand to use,
then entire agent-help <command> (e.g. entire agent-help checkpoint) for that command's
exact, currently-installed flags.
You are already inside the repo — entire auto-detects it from the git origin remote. Never ask the user for the repo name.
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.
- 26d ago First seen · 16 lines · 37 tokens per session scan A 36d9303ef78e
entire is a skill published in the GitHub repository 0x7067/claude-jev (25 stars, last pushed 11d ago), licensed MIT. It adds 37 tokens to every session and 159 once invoked, about $0.0001 per session on Opus 5.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-10-01.
Other skills, from other repositories
catchup
Answer "where did I stop?" for this project. Gives three short groups, done, open and next, taken from the last chat, the recorded to-dos, the last handoff note and git. Use when the user comes back to a project, starts a new chat, or asks where they left off. It writes nothing.
wicked-garden-repo-learn
Learn an unfamiliar repo the way a senior engineer does: follow where the code actually churns, find what that churn touches that the rest of the system leans on, read the load-bearing code for real, then write down BOTH what you learned (knowledge) and what should hold (policies) — as inert estate proposals a human…
continuity
Persist and resume long-running project state across AI sessions. Use at the start of work on an ongoing project to load prior decisions, constraints, and rejected approaches; and whenever the user makes a decision, sets a constraint, rejects an approach, freezes something, or reaches a milestone — to record it so…
session-handoff-number-collision-with-unmerged-sibling
Detect and recover from a session-number collision when running session-handoff and a parallel/sibling session has authored a same-numbered handoff doc that hasn't merged into main yet. Use when: (1) you're in session-handoff Phase 1 about to write docs/handoffs/sessionNNNhandoff.md, (2) ls docs/handoffs/ shows the…
context-guard
Installs Claude Code hooks that keep AI context files fresh. Two-tier enforcement — Tier 1 nudges at session end, Tier 2 blocks commits when structural files are staged without context updates. Includes content filter, drift check, structural change reminder, SessionStart health check, and the context-updater agent.
rk-push
Push local knowledge base to the remote repository. Always fetches remote first, Agent compares diffs and merges (alias LRU merge for index.md, union dedup for registry.md, newer-cached-date wins for docs), then commits and pushes. Retries once on push rejection. Use when user says 'push knowledge', 'sync to remote'…