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/prime-radiant-inc/streamlinear/linearnpx skills add prime-radiant-inc/streamlinear --skill lineargit clone --depth 1 https://github.com/prime-radiant-inc/streamlinearWhat 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.00019 | $0.00656 |
| Opus 5 | $0.00010 | $0.00328 |
| Sonnet 5 | $0.00004 | $0.00131 |
| Haiku 4.5 | $0.00002 | $0.00066 |
Grade A, and why
linear 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 3d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Linear CLI
Command-line interface for Linear issue management.
Search Issues
# Your active issues (default)
streamlinear-cli search
# Text search
streamlinear-cli search "auth bug"
# Filter by state
streamlinear-cli search --state "In Progress"
# Filter by assignee
streamlinear-cli search --assignee me
streamlinear-cli search --assignee [email protected]
# Filter by team
streamlinear-cli search --team ENG
# Combine filters
streamlinear-cli search --state "In Progress" --assignee me --team ENG
Get Issue Details
# By short ID
streamlinear-cli get ABC-123
# By URL
streamlinear-cli get "https://linear.app/team/issue/ABC-123"
Update Issue
# Change state
streamlinear-cli update ABC-123 --state Done
streamlinear-cli update ABC-123 --state "In Progress"
# Change priority (1=Urgent, 2=High, 3=Medium, 4=Low)
streamlinear-cli update ABC-123 --priority 1
# Assign to me
streamlinear-cli update ABC-123 --assignee me
# Assign to someone else
streamlinear-cli update ABC-123 --assignee [email protected]
# Unassign
streamlinear-cli update ABC-123 --assignee null
# Multiple updates
streamlinear-cli update ABC-123 --state Done --priority 3
Comment on Issue
streamlinear-cli comment ABC-123 "Fixed in commit abc123"
streamlinear-cli comment ABC-123 "Blocked on dependency update"
Create Issue
# Basic
streamlinear-cli create --team ENG --title "Bug: Login fails"
# With description
streamlinear-cli create --team ENG --title "Bug: Login fails" --body "Users see error on submit"
# With priority
streamlinear-cli create --team ENG --title "Urgent fix" --priority 1
List Teams
streamlinear-cli teams
Raw GraphQL
streamlinear-cli graphql "query { viewer { name email } }"
streamlinear-cli graphql "query { projects { nodes { id name } } }"
Priority Reference
| Value | Label |
|---|---|
| 0 | No priority |
| 1 | Urgent |
| 2 | High |
| 3 | Medium |
| 4 | Low |
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.
- 3d ago First seen · 126 lines · 19 tokens per session scan A 55966e560198
linear is a skill published in the GitHub repository prime-radiant-inc/streamlinear (89 stars, last pushed 6d ago), licensed MIT. It adds 19 tokens to every session and 656 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
linear-cli
Manage Linear issues from the command line using the linear cli. This skill allows automating linear management.
Release
This skill should be used when the user asks to "make a release", "create a release", "cut a release", "release a new version", "publish a release", or mentions preparing for release. Provides comprehensive workflow for reviewing changes, updating changelog, determining semver bump, and publishing.
linear
Read Linear issues, transition state, and post comments. The entry point for ticket-driven agent workflows.
cloud-storage-hexagonal-architecture
Enforce hexagonal architecture in the Rust backend. Use before modifying crates or Rust services, especially inbound axum/tool/listener adapters, domain services/ports, outbound adapters, authorization, permissions, database access, or external clients.
mintlify
Build and maintain documentation sites with Mintlify. Use when creating docs pages, configuring navigation, adding components, or setting up API references.
live-debug
Debug the running local stack with traces, logs, and a shared headless browser. Use when investigating a bug in a running service, tracing a request across services, reading service logs, reproducing a frontend issue, or writing/reviewing tracing instrumentation.