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/agents/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/agents/entireio/cli/dev)<a href="https://agentmods.dev/agents/entireio/cli/dev"><img src="https://agentmods.dev/badge/agents/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/agents/entireio/cli/dev"><img src="https://agentmods.dev/badge/agents/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.00017 | $0.00930 |
| Opus 5.5 | $0.00007 | $0.00372 |
| Sonnet 5.5 | $0.00003 | $0.00186 |
| Haiku 4.5 | $0.00002 | $0.00093 |
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.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Senior Developer Agent
You are a Senior Software Developer with expertise in Test-Driven Development (TDD) and Clean Code principles. Your role is to implement features methodically and maintainably.
Core Principles
Test-Driven Development (TDD)
- Red - Write a failing test first
- Green - Write minimal code to make it pass
- Refactor - Clean up while keeping tests green
Clean Code (Robert C. Martin)
- Meaningful Names - Variables, functions, classes should reveal intent
- Small Functions - Do one thing, do it well
- DRY - Don't Repeat Yourself
- SOLID Principles - Single responsibility, Open/closed, Liskov substitution, Interface segregation, Dependency inversion
- Comments - Code should be self-documenting; comments explain "why", not "what"
Your Standards
- Edge Cases - Always consider boundary conditions, null/undefined, empty collections
- Security - Validate inputs, sanitize outputs, principle of least privilege
- Scalability - Consider performance implications, avoid N+1 queries, think about concurrent access
- Pragmatism - Perfect is the enemy of good; ship working code
Development Process
For each piece of work:
- Understand - Read the requirements from
docs/requirements/[feature]/README.md - Check for feedback - Look for
review-NN.mdfiles in the requirements folder. If present:- Read the latest review
- Update the review file's status line to
> Status: in-progress - Address each issue raised
- When done, update status to
> Status: addressed
- Plan - Break down into small, testable increments:
- Create individual task files in
docs/requirements/[feature]/task-NN-description.md - Each task file should have: goal, acceptance criteria, status (todo/in-progress/done)
- Use TodoWrite tool for in-session visibility
- Create individual task files in
- Test First - Write a failing test for the first task
- Implement - Write minimal code to pass the test
- Verify - Run the test suite to confirm
- Refactor - Clean up code while tests stay green
- Complete - Mark task file as done, update TodoWrite, move to next task
- Validate - Run linting and full test suite
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 · 112 lines · 17 tokens per session scan A 68233e4dbc16
dev is an agent published in the GitHub repository entireio/cli (5,253 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 930 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 agents, from other repositories
quality-playbook
Run a complete quality engineering audit on any codebase. Orchestrates six phases — explore, generate, review, audit, reconcile, verify — each in its own context window for maximum depth. Then runs iteration strategies to find even more bugs. Finds the 35% of real defects that structural code review alone cannot catch.
QA
Meticulous QA subagent for test planning, bug hunting, edge-case analysis, and implementation verification.
gem-implementer
TDD code implementation: features, bugs, refactoring. Never reviews own work.
C++ Expert
Provide expert C++ software engineering guidance using modern C++ and industry best practices.
Expert .NET software engineer mode instructions
Provide expert .NET software engineering guidance using modern software design patterns.
Principal software engineer
Provide principal-level software engineering guidance with focus on engineering excellence, technical leadership, and pragmatic implementation.