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 chrisdoc/hevy-mcp --skill using-entiregit clone --depth 1 https://github.com/chrisdoc/hevy-mcpWrote 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/chrisdoc/hevy-mcp/using-entire)<a href="https://agentmods.dev/skills/chrisdoc/hevy-mcp/using-entire"><img src="https://agentmods.dev/badge/skills/chrisdoc/hevy-mcp/using-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/chrisdoc/hevy-mcp/using-entire"><img src="https://agentmods.dev/badge/skills/chrisdoc/hevy-mcp/using-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.00132 | $0.01749 |
| Opus 5.5 | $0.00053 | $0.00700 |
| Sonnet 5.5 | $0.00026 | $0.00350 |
| Haiku 4.5 | $0.00013 | $0.00175 |
Grade A, and why
using-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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- using-entire — 86% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using Entire
Your default when exploring or understanding code should be: read the recorded intent, don't guess.
Entire checkpoints capture the prompts, transcripts, and decisions behind every agent-driven change. When you need to understand why code exists or how a module evolved, look up the checkpoint history first. Only fall back to inference from code structure when no history is available — and label that explicitly.
When This Skill Activates
Use this skill whenever the task involves:
- A request phrased as "research X", "investigate X", "look into X", "dig into X", or "find out how X works"
- Exploring or understanding an unfamiliar module or file
- Preparing to refactor, extend, or debug code you didn't write
- Answering "why is this like this?" or "what was the intent?"
- Doing pre-work research before making changes
- Any codebase exploration where historical context would help
For a research- or investigate-shaped request, the very first action is an
entire search via the search skill. Do not open source files or grep first;
the recorded history says what was tried and why, and code reads come after to
confirm it.
Do not use this skill for simple, well-understood edits where you already have full context (e.g. "add a comment to line 5").
First Step: Check Repository Status
Before diving into specific lookups, check whether Entire is available and the repository has checkpoint history:
entire status
This tells you whether Entire is enabled, which git hooks are installed, whether the metadata branch is initialized, and any active sessions on the current branch.
Scenario Routing
When this skill activates, determine which sub-skill best fits the user's need:
| Scenario | Typical user expressions | Delegate to |
|---|---|---|
| Code block provenance | "why is this like this" / "wtf is going on" / "what happened at src/auth.ts:42" / "tell me why this changed" | what-happened |
| Research or investigate a topic | "research X" / "investigate X" / "look into X" / "dig into X" / "what do we know about X" | search first, then this skill's exploration flow if needed |
| Find prior work | "has anyone done X before" / "search past work for rate limiting" / "find the previous implementation" | search |
| Recall a task playbook | "have we done this before" / "recall how we did X" / "how did we do this last time" | recall |
| Replay feature history | "replay " / "walk me through how X was built" / "show me the journey of Y" | replay |
| Teach a repo topic | "teach me " / "how does work in this repo" / "give me a lesson on X" | teach |
| Understand original intent | "explain this function" / "explain parseConfig" / "what was the intent behind src/auth.ts" | explain |
| Generate a dispatch / summary | "summarize recent work" / "generate a dispatch" / "what was accomplished this week" | run entire dispatch directly |
| Code review with intent context | "review these changes" / "review this branch" / "audit before merging" | review |
| Hand off to another agent | "hand off this session" / "continue in another agent" / "pick up the codex session" | session-handoff |
| Convert session to skill | "turn this into a skill" / "make a skill from this session" | session-to-skill |
| Link session to other repos | "link session to other repos" / "attach session to the foo repo" | session-crosslink |
| General exploration | "understand this module" / "explore how auth works" / "help me understand the codebase" | (self — see below) |
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.
- 1mo ago First seen · 166 lines · 132 tokens per session scan A 97089b6cf325
using-entire is a skill published in the GitHub repository chrisdoc/hevy-mcp (523 stars, last pushed 2d ago), licensed MIT. It adds 132 tokens to every session and 1,749 once invoked, about $0.0005 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-09-07.
Other skills, from other repositories
verify
Run the checks that have to pass before a FreeReps commit lands — Go build, vet, tests and golangci-lint, the frontend type check and build, and the document contract check. Triggers — "verify", "prüf das durch", "vor dem commit", "läuft das durch", "check before committing", "run the checks", "does CI pass". Not for…
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
opik-diagnose
Surface the Opik traces worth a developer's attention, ranked by signal — Diagnostics issues first, then errors, failed tool calls, latency, regressions, and low online-eval scores. With the Opik MCP connected it lists the project's agentinsightsissue entities, offers to turn Diagnostics on when the project has it…
ue-mcp-epic-routing
Use when deciding between ue-mcp's native category actions and Epic's wrapped ToolsetRegistry tools (the epic actions, incl. the Blueprint graph DSL) for a task in Unreal. Pulls in when authoring Blueprint graph bodies, or any time both a native action and an epic action could do the job and you need to pick.
qa-knowledge
To run QA engineering — requirements/gap analysis, scenario & spec design, test implementation, failure triage — over the QA knowledge base.
frontmcp-setup
Use when starting, scaffolding, or organizing a FrontMCP project. Covers creating a new project (CLI scaffold or manual) for Node, Vercel, and other targets; standalone versus Nx-monorepo layout, naming conventions, generators, and dependency rules; composing multiple @App classes, ESM packages, and remote MCP servers…