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/packtpublishing/agentic-coding-with-claude-code/infinitegit clone --depth 1 https://github.com/PacktPublishing/Agentic-Coding-with-Claude-CodeWrote 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/packtpublishing/agentic-coding-with-claude-code/infinite)<a href="https://agentmods.dev/commands/packtpublishing/agentic-coding-with-claude-code/infinite"><img src="https://agentmods.dev/badge/commands/packtpublishing/agentic-coding-with-claude-code/infinite.svg" alt="Measured on agentmods" 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.00000 | $0.01560 |
| Opus 5 | $0.00000 | $0.00780 |
| Sonnet 5 | $0.00000 | $0.00312 |
| Haiku 4.5 | $0.00000 | $0.00156 |
Grade A, and why
infinite 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
INFINITE AGENTIC LOOP COMMAND
Think deeply about this infinite generation task. You are about to embark on a sophisticated iterative creation process.
Variables:
spec_file: $ARGUMENTS output_dir: $ARGUMENTS count: $ARGUMENTS
ARGUMENTS PARSING: Parse the following arguments from "$ARGUMENTS":
spec_file- Path to the markdown specification fileoutput_dir- Directory where iterations will be savedcount- Number of iterations (1-N or "infinite")
PHASE 1: SPECIFICATION ANALYSIS
Read and deeply understand the specification file at spec_file. This file defines:
- What type of content to generate
- The format and structure requirements
- Any specific parameters or constraints
- The intended evolution pattern between iterations
Think carefully about the spec's intent and how each iteration should build upon previous work.
PHASE 2: OUTPUT DIRECTORY RECONNAISSANCE
Thoroughly analyze the output_dir to understand the current state:
- List all existing files and their naming patterns
- Identify the highest iteration number currently present
- Analyze the content evolution across existing iterations
- Understand the trajectory of previous generations
- Determine what gaps or opportunities exist for new iterations
PHASE 3: ITERATION STRATEGY Based on the spec analysis and existing iterations:
- Determine the starting iteration number (highest existing + 1)
- Plan how each new iteration will be unique and evolutionary
- Consider how to build upon previous iterations while maintaining novelty
- If count is "infinite", prepare for continuous generation until context limits
PHASE 4: PARALLEL AGENT COORDINATION Deploy multiple Sub Agents to generate iterations in parallel for maximum efficiency and creative diversity:
Sub-Agent Distribution Strategy:
- For count 1-5: Launch all agents simultaneously
- For count 6-20: Launch in batches of 5 agents to manage coordination
- For "infinite": Launch waves of 3-5 agents, monitoring context and spawning new waves
Agent Assignment Protocol: Each Sub Agent receives:
- Spec Context: Complete specification file analysis
- Directory Snapshot: Current state of output_dir at launch time
- Iteration Assignment: Specific iteration number (starting_number + agent_index)
- Uniqueness Directive: Explicit instruction to avoid duplicating concepts from existing iterations
- Quality Standards: Detailed requirements from the specification
Agent Task Specification:
TASK: Generate iteration [NUMBER] for [SPEC_FILE] in [OUTPUT_DIR]
You are Sub Agent [X] generating iteration [NUMBER].
CONTEXT:
- Specification: [Full spec analysis]
- Existing iterations: [Summary of current output_dir contents]
- Your iteration number: [NUMBER]
- Assigned creative direction: [Specific innovation dimension to explore]
REQUIREMENTS:
1. Read and understand the specification completely
2. Analyze existing iterations to ensure your output is unique
3. Generate content following the spec format exactly
4. Focus on [assigned innovation dimension] while maintaining spec compliance
5. Create file with exact name pattern specified
6. Ensure your iteration adds genuine value and novelty
DELIVERABLE: Single file as specified, with unique innovative content
Parallel Execution Management:
- Launch all assigned Sub Agents simultaneously using Task tool
- Monitor agent progress and completion
- Handle any agent failures by reassigning iteration numbers
- Ensure no duplicate iteration numbers are generated
- Collect and validate all completed iterations
PHASE 5: INFINITE MODE ORCHESTRATION For infinite generation mode, orchestrate continuous parallel waves:
Wave-Based Generation:
- Wave Planning: Determine next wave size (3-5 agents) based on context capacity
- Agent Preparation: Prepare fresh context snapshots for each new wave
- Progressive Sophistication: Each wave should explore more advanced innovation dimensions
- Context Monitoring: Track total context usage across all agents and main orchestrator
- Graceful Conclusion: When approaching context limits, complete current wave and summarize
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 · 181 lines · 0 tokens per session scan A e07faf0c6ef5
infinite is a command published in the GitHub repository PacktPublishing/Agentic-Coding-with-Claude-Code (186 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,560 tokens. 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-09-04.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.