Entire CLI connects AI coding-agent sessions to Git so prompts, responses, files, tool calls, and checkpoints become a searchable record alongside commits. Developers and teams use it to understand why code changed, resume earlier sessions, keep agent context out of Git history, and support traceability. The catalogue includes commands, hooks, skills, agents, and plugins for the Entire workflow.
Borrowing it
Nothing to install: this file belongs to entireio/cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/entireio/cli/main/.claude/skills/test-repo/SKILL.mdgit clone --depth 1 https://github.com/entireio/cliWrote 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/entireio/cli/test-repo)<a href="https://agentmods.dev/skills/entireio/cli/test-repo"><img src="https://agentmods.dev/badge/skills/entireio/cli/test-repo/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/entireio/cli/test-repo"><img src="https://agentmods.dev/badge/skills/entireio/cli/test-repo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00050 | $0.01731 |
| Opus 5.5 | $0.00020 | $0.00692 |
| Sonnet 5.5 | $0.00010 | $0.00346 |
| Haiku 4.5 | $0.00005 | $0.00173 |
Grade A, and why
test-repo 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 19d 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.
How it starts
The opening of the file, as written. The whole thing — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Repository Skill
This skill validates the CLI's session management and checkpoint creation by running an end-to-end test against a fresh temporary repository.
When to Use
- User asks to "test against a test repo"
- User wants to validate strategy changes (manual-commit)
- User asks to verify session hooks, commits, or checkpoint creation
- After making changes to strategy code
Testing Approaches
Automated Testing (recommended for validation):
mise run test:integration
Run the comprehensive integration test suite. Best for verifying correctness after code changes.
Manual Testing (this skill): Use the test harness for:
- Debugging specific strategy behaviors
- Interactive exploration of the checkpoint workflow
- Manual verification of edge cases
- Understanding how the system works step-by-step
Test Procedure
Setup
Step 1: Build the CLI
go build -o /tmp/entire-bin ./cmd/entire
Step 2: Approve the test harness (one-time)
Add this pattern to your Claude Code approved commands, or approve it once when prompted:
{
"approvedBashCommands": [
".claude/skills/test-repo/test-harness.sh*"
]
}
Optional: Set strategy (defaults to manual-commit):
export STRATEGY=manual-commit
Test Steps
Execute these steps in order:
1. Setup Test Environment
.claude/skills/test-repo/test-harness.sh setup-repo
.claude/skills/test-repo/test-harness.sh configure-strategy
2. Simulate Session
.claude/skills/test-repo/test-harness.sh start-session
.claude/skills/test-repo/test-harness.sh create-files
.claude/skills/test-repo/test-harness.sh create-transcript
.claude/skills/test-repo/test-harness.sh stop-session
3. Verify Results
.claude/skills/test-repo/test-harness.sh verify-commit
.claude/skills/test-repo/test-harness.sh verify-session-state
.claude/skills/test-repo/test-harness.sh verify-no-shadow-branch
.claude/skills/test-repo/test-harness.sh list-pending-checkpoints
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 19d ago Changed · -4 lines e87d8a052e2a
- 1mo ago Changed · -10 lines 017729ff2f7d
- 1mo ago First seen · 231 lines · 50 tokens per session scan A 60db1c8cf563
test-repo is a skill published in the GitHub repository entireio/cli (5,253 stars, last pushed today), licensed MIT. It adds 50 tokens to every session and 1,731 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
coverage-drop-investigator
Use when test coverage has dropped and you need to find which changes caused it and what tests to add. Traces coverage regressions to specific commits and files.
cmux-testing
Choose scoped cmux verification, add behavioral tests, and validate Swift test targets and wiring. Use when adding tests or deciding what local/CI evidence a change needs.
cast-ship
Take finished work through to merge. Commits in topical pieces, opens the pull request with a description that links the session, then binds this session to the pull request so review comments, failing checks and a stale branch wake it until the merge lands. Use when asked to ship, open a PR, or handle review…
hex-execute
Multi-agent execution orchestrator — implements an approved hex-plan artifact (or a free-text task) as parallel pipelines of serial steps cut along contracts, merges them onto a feature branch, runs one integration gate concurrent with one review, and hands to /hex-finalize. Use to execute, implement, build, or run an…
jira-delivery
Close the needs-fix branch for both ticket classes: isolated git worktree, a red test BEFORE any implementation on change tickets, delegation to a core executor, every publish action (push / PR / comment / QA transition) gated behind a green @verification-agent verdict, commit + push + PR, then writeback via…
build-ticket
Build Skill: Implements tickets using TDD methodology. Commits code to the current branch. MANDATORY TRIGGERS: build, implement, code, develop, work ticket, TDD, red green refactor, fix bug, write code.