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 agentmods add commands/entireio/cli/dev-cyclegit clone --depth 1 https://github.com/entireio/cliWhat 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 | $0.00016 | $0.00942 |
| Opus 5 | $0.00008 | $0.00471 |
| Sonnet 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 yesterday.
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.
- yesterday First seen · 131 lines · 16 tokens per session scan A 0a0c9c8f8959
dev-cycle is a command published in the GitHub repository entireio/cli (5,038 stars, last pushed 2d ago), licensed MIT. It adds 16 tokens to every session and 942 once invoked, about $0.0001 per session on Opus 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
example-command
An example slash command that demonstrates command frontmatter options (legacy format).
default-cmd
In the default commands dir, which the declared path replaces.
code-review-swarm
Deploy specialized AI agents to perform comprehensive, intelligent code reviews that go beyond traditional static analysis.
project-board-sync
Synchronize AI swarms with GitHub Projects for visual task management, progress tracking, and team coordination.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
release-swarm
Orchestrate complex software releases using AI swarms that handle everything from changelog generation to multi-platform deployment.