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 skills add nesszer/linear-cli --skill linear-sprintgit clone --depth 1 https://github.com/nesszer/linear-cliWrote 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/skills/nesszer/linear-cli/linear-sprint)<a href="https://agentmods.dev/skills/nesszer/linear-cli/linear-sprint"><img src="https://agentmods.dev/badge/skills/nesszer/linear-cli/linear-sprint/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/skills/nesszer/linear-cli/linear-sprint"><img src="https://agentmods.dev/badge/skills/nesszer/linear-cli/linear-sprint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00028 | $0.00345 |
| Opus 5.5 | $0.00011 | $0.00138 |
| Sonnet 5.5 | $0.00006 | $0.00069 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
linear-sprint 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.
What it actually says
Sprint Planning
# Current sprint status
linear-cli sp status -t ENG
# Sprint progress (completion bar)
linear-cli sp progress -t ENG
# Plan next sprint (view planned issues)
linear-cli sp plan -t ENG
# Carry over incomplete issues to next cycle
linear-cli sp carry-over -t ENG --force
# ASCII burndown chart
linear-cli sp burndown -t ENG
# Velocity across recent sprints
linear-cli sp velocity -t ENG
linear-cli sp velocity -t ENG --cycles 10 # Last 10 sprints
linear-cli sp velocity -t ENG --output json
Subcommands
| Command | Purpose |
|---|---|
status |
Current sprint overview |
progress |
Visual completion bar |
plan |
Next cycle's planned issues |
carry-over |
Move incomplete to next cycle |
burndown |
ASCII burndown chart |
velocity |
Sprint velocity + trend analysis |
Flags
| Flag | Purpose |
|---|---|
-t TEAM |
Team key (required) |
--cycles N |
Number of past cycles for velocity |
--force |
Skip carry-over confirmation |
--output json |
JSON output |
Exit Codes
0=Success, 1=Error, 2=Not found, 3=Auth error
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 · 54 lines · 28 tokens per session scan A 9f93f752e452
linear-sprint is a skill published in the GitHub repository nesszer/linear-cli (138 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 345 once invoked, about $0.0001 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-30.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…