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/commands/dev.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/commands/entireio/cli/dev)<a href="https://agentmods.dev/commands/entireio/cli/dev"><img src="https://agentmods.dev/badge/commands/entireio/cli/dev/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/commands/entireio/cli/dev"><img src="https://agentmods.dev/badge/commands/entireio/cli/dev.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.00015 | $0.00238 |
| Opus 5.5 | $0.00006 | $0.00095 |
| Sonnet 5.5 | $0.00003 | $0.00048 |
| Haiku 4.5 | $0.00002 | $0.00024 |
Grade A, and why
dev 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.
What it actually says
ACTION REQUIRED: Spawn a subagent using the Task tool.
Do NOT implement code directly. Instead, immediately call the Task tool with:
Task(
subagent_type: "general-purpose",
description: "Developer implementing [feature]",
prompt: "
Read and follow the instructions in .claude/agents/dev.md
Requirements folder: $ARGUMENTS
Your task:
1. Read .claude/agents/dev.md for your role and process
2. Read $ARGUMENTS/README.md for requirements
3. Check for existing task files and review files in $ARGUMENTS/
4. If review-NN.md exists, address that feedback first
5. Create/update task breakdown files
6. Implement using TDD (test first, then code)
7. Run tests and linting after each step
8. Report what you built when done
"
)
Replace $ARGUMENTS with: $ARGUMENTS
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 · 32 lines · 15 tokens per session scan A c74c549dd1c5
dev is a command published in the GitHub repository entireio/cli (5,181 stars, last pushed today), licensed MIT. It adds 15 tokens to every session and 238 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-08-30.
Other commands, from other repositories
tdd
Test-driven development with TodoWrite planning and comprehensive testing.
examples
Real-world examples and scenarios for pair programming sessions.
start
Start a new pair programming session with AI assistance.
workflow-implement
Exécuter la phase d'Implémentation - développement sprint avec TDD/BDD.
tdd
Correction de Bug en Mode TDD/BDD.
fix
Correction automatisee des bugs identifies par la QA Recette.