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-cycle.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-cycle)<a href="https://agentmods.dev/commands/entireio/cli/dev-cycle"><img src="https://agentmods.dev/badge/commands/entireio/cli/dev-cycle/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-cycle"><img src="https://agentmods.dev/badge/commands/entireio/cli/dev-cycle.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.00016 | $0.00942 |
| Opus 5.5 | $0.00006 | $0.00377 |
| Sonnet 5.5 | $0.00003 | $0.00188 |
| Haiku 4.5 | $0.00002 | $0.00094 |
Grade A, and why
dev-cycle 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Development Cycle Orchestrator
You are orchestrating a development cycle between a Developer agent and a Code Reviewer agent. Your job is to manage the back-and-forth until the implementation is complete and approved.
The Cycle
┌─────────────────┐
│ Requirements │
└────────┬────────┘
│
▼
┌─────────────────┐
│ Developer │◄─────────┐
│ Implements │ │
└────────┬────────┘ │
│ │
▼ │
┌─────────────────┐ │
│ Reviewer │ │
│ Critiques │ │
└────────┬────────┘ │
│ │
▼ │
┌─────────┐ │
│Approved?│──── No ──────┘
└────┬────┘
│ Yes
▼
┌─────────────────┐
│ Done │
└─────────────────┘
Agent Instructions
- Developer:
.claude/agents/dev.md - Reviewer:
.claude/agents/reviewer.md
Your Process
Phase 1: Setup
- Read the requirements from: $ARGUMENTS/README.md
- Understand what needs to be built
- Create feature branch (if not already on one):
# Extract feature name from path (e.g., "jaja-bot" from "docs/requirements/jaja-bot") git checkout -b feature/[feature-name] - Review any existing task files and review files in $ARGUMENTS/
Phase 2: Development Loop
For each iteration:
-
Invoke Developer Agent Use the Task tool:
Task( subagent_type: "general-purpose", prompt: " Read and follow .claude/agents/dev.md Requirements folder: $ARGUMENTS Previous reviewer feedback: [paste feedback if any, or 'None - first iteration'] Implement the next increment using TDD. Report what you built when done. " ) -
Invoke Reviewer Agent Use the Task tool:
Task( subagent_type: "general-purpose", prompt: " Read and follow .claude/agents/reviewer.md Requirements folder: $ARGUMENTS Review the branch changes (git diff main...HEAD -- . ':!.entire'). Provide structured feedback with verdict: APPROVE or REQUEST CHANGES " )
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 · 131 lines · 16 tokens per session scan A 0a0c9c8f8959
dev-cycle is a command published in the GitHub repository entireio/cli (5,181 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 942 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
code-review-swarm
Deploy specialized AI agents to perform comprehensive, intelligent code reviews that go beyond traditional static analysis.
pr-manager
Comprehensive pull request management with ruv-swarm coordination for automated reviews, testing, and merge workflows.
COMMAND_COMPLIANCE_REPORT
Reviewed all command files in .claude/commands/analysis/ directory to ensure proper usage of.
reviewer
Code review using batch file analysis for comprehensive reviews.
code-review
Automated code review with swarm intelligence.
pr-enhance
Command "pr-enhance" from ruvnet/agentic-flow, covering pr-enhance, usage, options, examples and enhance pr.