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 skills/mountainunicorn/add/cyclenpx skills add MountainUnicorn/add --skill cyclegit clone --depth 1 https://github.com/MountainUnicorn/addWhat 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.00023 | $0.04909 |
| Opus 5 | $0.00012 | $0.02455 |
| Sonnet 5 | $0.00005 | $0.00982 |
| Haiku 4.5 | $0.00002 | $0.00491 |
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.
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
--statusand--complete) .add/learnings.mdcheckpoint entries (filled in by--complete)
Pre-Flight: Context & Setup
All cycle commands start by reading context:
- Read
.add/config.jsonto find current maturity level- This governs cycle scope, parallelism limits, and documentation depth
- 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)
- Find the current milestone (look for
- Milestone health check — after loading the active milestone, check its status:
- No active milestone (
planning.current_milestoneis null or file doesn't exist): Display "No active milestone found." Offer: run/add:milestone --listto see available milestones,/add:milestone --switch <id>to activate one, or/add:milestone --createto 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 --completeor switching to the next one."
- No active milestone (
- 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
- Verify prerequisites (e.g., if POC maturity, skip some docs)
- Check for session handoff — per the Session-Handoff Preflight in
${CLAUDE_PLUGIN_ROOT}/references/skill-epilogue.md
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.
- 2d ago First seen · 463 lines · 23 tokens per session scan A d55f4be2800f
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.
Other skills, from other repositories
team
Referencing the agent roster, roles, coordination model, and dispatch modes. Use when spawning agents or checking permissions.
ticket
Associate every PDS task with a GitHub issue. Orchestrator finds or creates the ticket, posts plan and acceptance criteria as a checkbox list, updates it as work progresses. Use at Phase 1 of every swarm.
triage
Triage insights into actionable GitHub issues across repos. Use after running /insights to convert analysis into tracked work.
taiyi-plan
TaiyiForge /taiyi:plan — 项目规划入口:把 README/PRD 拆解为独立 change 清单,推荐 profile 和依赖关系。OpenCode / Claude / Codex / Cursor 通用。.
taiyi-task
TaiyiForge 第5阶段 — 任务拆解,TASK.md。四端通用。.
taiyi-ultrawork
TaiyiForge ultrawork — 并行切片 + Cursor Task 自动派发契约(对标 OMC ultrawork + spawnagent).