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/nesszer/linear-cli/linear-cyclesnpx skills add nesszer/linear-cli --skill linear-cyclesgit clone --depth 1 https://github.com/nesszer/linear-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.00024 | $0.00276 |
| Opus 5 | $0.00012 | $0.00138 |
| Sonnet 5 | $0.00005 | $0.00055 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
linear-cycles 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.
What it actually says
Cycles
# List cycles
linear-cli c list -t ENG # Team cycles
linear-cli c list -t ENG --output json
# Current cycle
linear-cli c current -t ENG
linear-cli c current -t ENG --output json
# Create cycle
linear-cli c create -t ENG --name "Sprint 5"
linear-cli c create -t ENG --name "Sprint 5" --starts-at 2024-01-01 --ends-at 2024-01-14
# Get cycle details
linear-cli c get CYCLE_ID
# Update cycle
linear-cli c update CYCLE_ID --name "Sprint 5b"
linear-cli c update CYCLE_ID --description "Updated goals" --dry-run
# Complete a cycle
linear-cli c complete CYCLE_ID
# Delete cycle
linear-cli c delete CYCLE_ID --force
Flags
| Flag | Purpose |
|---|---|
--output json |
JSON output |
--compact |
No formatting |
--dry-run |
Preview without updating |
--force |
Skip delete confirmation |
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 · 44 lines · 24 tokens per session scan A ee70f3371ca5
linear-cycles is a skill published in the GitHub repository nesszer/linear-cli (133 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 276 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
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
setup-matt-pocock-skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
accessibility
Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
bug-triage
Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.