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 diillson/chatcli --skill lineargit clone --depth 1 https://github.com/diillson/chatcliWrote 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/diillson/chatcli/linear)<a href="https://agentmods.dev/skills/diillson/chatcli/linear"><img src="https://agentmods.dev/badge/skills/diillson/chatcli/linear.svg" alt="Measured on agentmods" 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.00069 | $0.00513 |
| Opus 5 | $0.00034 | $0.00257 |
| Sonnet 5 | $0.00014 | $0.00103 |
| Haiku 4.5 | $0.00007 | $0.00051 |
Grade A, and why
linear scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s https://api.linear.app/graphql -H "Authorization: $LINEAR_API_KEY" \ What it actually says
Linear
Drive Linear through its GraphQL API with the user's own key — opt-in, no middleman.
Setup
Set LINEAR_API_KEY (Settings → API → Personal API keys). All calls:
curl -s https://api.linear.app/graphql -H "Authorization: $LINEAR_API_KEY" \
-H "Content-Type: application/json" -d '{"query":"..."}'
My open issues
{"query":"{ viewer { assignedIssues(filter:{state:{type:{neq:\"completed\"}}}) { nodes { identifier title state { name } } } } }"}
Search issues
{"query":"query($q:String!){ searchIssues(term:$q){ nodes{ identifier title url } } }","variables":{"q":"login bug"}}
Create an issue
First resolve the team id ({ teams { nodes { id key name } } }), then:
{"query":"mutation($t:String!,$ti:String!,$d:String){ issueCreate(input:{teamId:$t,title:$ti,description:$d}){ success issue{ identifier url } } }","variables":{"t":"TEAM_ID","ti":"Fix X","d":"details"}}
Update status / assignee / comment
- Resolve workflow state ids (
{ workflowStates { nodes { id name } } }), thenissueUpdate(input:{id, stateId}). - Comment:
commentCreate(input:{issueId, body}).
Rules
- If
LINEAR_API_KEYis unset, explain how to create one and stop. - Resolve human references (team key, status name,
LIN-123identifier) to ids before mutating. - Echo the issue identifier + URL after creating/updating.
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 · 57 lines · 69 tokens per session scan A 5effb584d893
linear is a skill published in the GitHub repository diillson/chatcli (90 stars, last pushed yesterday), licensed Apache-2.0. It adds 69 tokens to every session and 513 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
01-sdlc
Autonomously orchestrates a request from framing to a draft pull request, isolating implementation, independent review, and final outcome challenge. Use when the user wants to deliver a change end to end. Not for running one development step.
02-backlog
Orchestrates a product backlog end to end. Use when the user wants to ask what it holds, or to run intake, triage, refinement, review, lifecycle events, ordering, health checks, or repair. Not for one known artifact step.
02-user-stories
Produces or refines ordered User Stories from an Epic, Product Brief, PRD, or bounded request. Use when the user wants to slice, write, assess, order, or persist Stories. Not for Epics or implementation.
07-epic
Produces or refines an outcome-based Epic for a product backlog. Use when the user wants to frame, review, resume, or persist an Epic. Not for Product Briefs, User Stories, or implementation.
08-three-amigos
Assesses an Epic or Story through one product, delivery, or quality lens, then reconciles three caller-supplied reports. Use when the user wants to refine one before a backlog change. Not for spawning or writing.
09-defect
Produces or refines a backlog Defect from an observed product mismatch. Use when the user wants to report, assess, link, order, transition, or verify a defect. Not for incident response, debugging, or implementation.