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.
git clone --depth 1 https://github.com/ruslan-korneev/claude-pluginsWrote 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/ruslan-korneev/claude-plugins/cycle)<a href="https://agentmods.dev/commands/ruslan-korneev/claude-plugins/cycle"><img src="https://agentmods.dev/badge/commands/ruslan-korneev/claude-plugins/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/ruslan-korneev/claude-plugins/cycle"><img src="https://agentmods.dev/badge/commands/ruslan-korneev/claude-plugins/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.00011 | $0.00875 |
| Opus 5.5 | $0.00004 | $0.00350 |
| Sonnet 5.5 | $0.00002 | $0.00175 |
| Haiku 4.5 | $0.00001 | $0.00088 |
Grade A, and why
linear: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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command /linear:cycle
Manage Linear cycles (sprints).
Instructions
Step 0: Validate Configuration
Check LINEAR_API_KEY and LINEAR_TEAM are set.
Step 1: Resolve Team ID
Use teams query to resolve $LINEAR_TEAM to UUID.
Step 2: Execute Action
action=current (default)
Fetch cycles, find the active one (where startsAt <= today <= endsAt and completedAt is null). Fetch its issues.
Display:
## Current Cycle: Sprint 42
**Period**: Mar 4 — Mar 18, 2026
**Progress**: 12/20 issues completed
[████████████░░░░░░░░] 60%
### Breakdown by Status
| Status | Count | Points |
|--------|-------|--------|
| Done | 8 | 21 |
| In Review | 1 | 3 |
| In Progress | 4 | 13 |
| Todo | 2 | 3 |
| Backlog | 3 | 5 |
| **Total** | **18** | **45** |
### Remaining Work
| ID | Title | Status | Assignee | Pts |
|----|-------|--------|----------|-----|
| TEAM-123 | Auth flow | In Progress | John | 5 |
| TEAM-124 | Pagination | In Progress | Jane | 3 |
| ... |
action=list
Fetch all cycles for team. Display:
## Cycles
| # | Name | Period | Issues | Completed | Progress |
|---|------|--------|--------|-----------|----------|
| 42 | Sprint 42 | Mar 4-18 | 20 | 12 | 60% |
| 41 | Sprint 41 | Feb 18-Mar 3 | 18 | 17 | 94% |
| 40 | Sprint 40 | Feb 4-17 | 15 | 15 | 100% |
Mark current cycle with an indicator.
action=stats
Fetch last 5 completed cycles. Calculate:
- Velocity: average completed points per cycle
- Throughput: average completed issues per cycle
- Completion rate: average % of scope completed
Display:
## Cycle Statistics
### Velocity (last 5 cycles)
| Cycle | Points Completed | Issues Completed | Completion |
|-------|------------------|------------------|------------|
| Sprint 41 | 34 | 17 | 94% |
| Sprint 40 | 30 | 15 | 100% |
| Sprint 39 | 28 | 14 | 88% |
| Sprint 38 | 32 | 16 | 94% |
| Sprint 37 | 26 | 13 | 81% |
**Average velocity**: 30 points/cycle
**Average throughput**: 15 issues/cycle
**Average completion**: 91%
### By Assignee (current cycle)
| Assignee | Completed | In Progress | Points |
|----------|-----------|-------------|--------|
| John Doe | 5 | 2 | 18 |
| Jane Smith | 4 | 1 | 12 |
| Bob Wilson | 3 | 1 | 10 |
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 · 129 lines · 11 tokens per session scan A 7c47d592ee75
linear:cycle is a command published in the GitHub repository ruslan-korneev/claude-plugins (5 stars, last pushed 7mo ago), licensed MIT. It adds 11 tokens to every session and 875 once invoked, about $0.0000 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-31.
Other commands, from other repositories
spec
A requirements-planning command for OpenSpec, a tool that records software changes as proposals, specification updates, and task lists. It clarifies the request, challenges risky assumptions, and pauses for approval before implementation.
octo-schedule
Manage scheduled workflow jobs for the Claude Octopus scheduler.
octo-scheduler
Manage the Claude Octopus scheduled workflow runner daemon.
next
Read the active sprint’s current status. Refresh stale compilation using grainulator compile --dir or grainulator.compile. Use the resulting nextactions with the user’s current scope and authorization. Output only the two Auto and Manual lists below, with no recap, status counters or offer to continue. Continue useful…
specmanager-build
Build one phase of a SpecManager feature's plan via the builder subagent. Stops at the phase boundary; never advances.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.