cycle

A work-cycle manager for Agent Driven Development. A cycle is a planned batch of related work completed before a human review point, usually lasting one to seven days.

In plain words
What is it for?
Use it to plan a cycle, check its status, complete it, update the milestone plan, and record lessons learned.
Why use it?
It makes dependencies, parallel work, effort, and completion checks explicit before implementation begins.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/mountainunicorn/add/cycle
Any agent
npx skills add MountainUnicorn/add --skill cycle
Clone the repo
git clone --depth 1 https://github.com/MountainUnicorn/add

Made for: Claude Code, Codex.

Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,909 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00023 $0.04909
Opus 5 $0.00012 $0.02455
Sonnet 5 $0.00005 $0.00982
Haiku 4.5 $0.00002 $0.00491

Measured 2d ago against content hash d55f4be2800f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 2d 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.

core/skills/cycle/SKILL.md · 463 lines

How it starts

The opening of the file, as written. The whole thing — 463 lines — stays where its author put it; the contents beside it link to each section on GitHub.

ADD Cycle Command v{{VERSION}}

Cycles are the operational unit of ADD work. They batch features, assess dependencies, plan parallelism, and define validation criteria before execution. This command manages the full cycle lifecycle: planning, status checks, and completion/retrospective.


Overview: What is a Cycle?

A cycle is the next batch of work before a human checkpoint. It:

  • Picks features from the current milestone's hill chart
  • Maps dependencies (what must serialize vs. what can parallelize)
  • Assigns agents and effort estimates
  • Defines per-item and overall validation criteria
  • Ranges from 1-7 days depending on maturity and scope

Cycle outputs:

  • .add/cycles/cycle-{N}.md — the cycle plan (generated by --plan)
  • Updated milestone hill chart (filled in by --status and --complete)
  • .add/learnings.md checkpoint entries (filled in by --complete)

Pre-Flight: Context & Setup

All cycle commands start by reading context:

  1. Read .add/config.json to find current maturity level
    • This governs cycle scope, parallelism limits, and documentation depth
  2. Read active milestone from docs/milestones/
    • Find the current milestone (look for Status: IN_PROGRESS, or the most recent)
    • Fail gracefully if no active milestone (prompt to create one first)
  3. Milestone health check — after loading the active milestone, check its status:
    • No active milestone (planning.current_milestone is null or file doesn't exist): Display "No active milestone found." Offer: run /add:milestone --list to see available milestones, /add:milestone --switch <id> to activate one, or /add:milestone --create to create a new one. STOP cycle planning until a milestone is active.
    • Active milestone is COMPLETE (all success criteria checked): Display "Current milestone {name} is COMPLETE." Scan docs/milestones/ for NOT_STARTED milestones. If found, suggest switching. If none, suggest creating one. STOP cycle planning until milestone is switched.
    • All features at DONE/VERIFIED but milestone not formally complete: Display "All features in {name} appear complete. Consider closing this milestone with /add:cycle --complete or switching to the next one."
  4. Check for existing active cycle in .add/cycles/
    • If one exists and last activity was < 3 days ago, assume it's still active
    • Otherwise, offer to archive and start fresh
  5. Verify prerequisites (e.g., if POC maturity, skip some docs)
  6. Check for session handoff — per the Session-Handoff Preflight in ${CLAUDE_PLUGIN_ROOT}/references/skill-epilogue.md

Read the full file on GitHub · 463 lines

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.

  1. 2d ago First seen · 463 lines · 23 tokens per session scan A d55f4be2800f

Subscribe to this mod's changes

cycle is a skill published in the GitHub repository MountainUnicorn/add (11 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 4,909 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.