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/aksika/abtars/linearnpx skills add aksika/abtars --skill lineargit clone --depth 1 https://github.com/aksika/abtarsWhat 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.00014 | $0.00865 |
| Opus 5 | $0.00007 | $0.00432 |
| Sonnet 5 | $0.00003 | $0.00173 |
| Haiku 4.5 | $0.00001 | $0.00086 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Linear Workflow Management
Manage Linear issues and projects through the bundled CLI at {baseDir}/scripts/linear-cli.js.
Scope and Runtime Model
- This skill runs
node {baseDir}/scripts/linear-cli.js .... - The CLI uses the official
@linear/sdk. - Authentication is
LINEAR_API_KEYfrom the local environment. - Expected API destination is Linear GraphQL (
https://api.linear.app/graphql) through the official SDK.
Prerequisites
- Node.js and npm are installed.
- Install script dependencies once:
cd {baseDir}/scripts && npm install
- Set your API key:
export LINEAR_API_KEY="lin_api_..."
If dependencies or LINEAR_API_KEY are missing, stop and complete setup before issue/project operations.
Authentication and Credentials
- Required credential:
LINEAR_API_KEY. - Get it from
https://linear.app/settings/api. - Use least-privilege access and a dedicated token for automation.
Required Workflow
- Clarify intent and scope:
- Team/project, labels, cycle, assignee, due date, priority.
- Read current state first:
- List/get issues, projects, statuses, labels, users, cycles.
- Apply mutations second:
- Create/update issues, comments, projects, milestones, labels.
- Summarize exactly what changed:
- Mention IDs, states, assignees, blockers, and follow-up actions.
Command Coverage
- Teams and projects:
teams,projects,createProject - Issues:
issues,issue,createIssue,updateIssue - Comments:
createComment - States and labels:
states,labels - User:
user
Quick Examples
node {baseDir}/scripts/linear-cli.js teams
node {baseDir}/scripts/linear-cli.js projects
node {baseDir}/scripts/linear-cli.js issues
node {baseDir}/scripts/linear-cli.js issue ENG-123
node {baseDir}/scripts/linear-cli.js createIssue "Title" "Description" "team-id" '{"priority":2}'
node {baseDir}/scripts/linear-cli.js updateIssue "issue-id" '{"stateId":"state-id"}'
Practical Workflows
- Triage urgent bugs:
list high-priority open issues, assign owners, move state to
In Progress, add triage comments. - Sprint planning: review cycle scope, create missing issues, set priorities and estimates, align assignees.
- Release prep: verify blockers, update project status, create milestone tasks, add rollout comments.
- Documentation cleanup: find stale docs/issues, open follow-up tasks, link related records.
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 · 91 lines · 14 tokens per session scan A dcaa7c1bce7c
linear is a skill published in the GitHub repository aksika/abtars (9 stars, last pushed 2d ago), licensed Apache-2.0. It adds 14 tokens to every session and 865 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-31.
Other skills, from other repositories
agent-quorum-manager
Agent skill for quorum-manager - invoke with $agent-quorum-manager.
agent-agent
Agent skill for agent - invoke with $agent-agent.
agent-crdt-synchronizer
Agent skill for crdt-synchronizer - invoke with $agent-crdt-synchronizer.
agent-adaptive-coordinator
Agent skill for adaptive-coordinator - invoke with $agent-adaptive-coordinator.
agent-performance-monitor
Agent skill for performance-monitor - invoke with $agent-performance-monitor.
agent-code-review-swarm
Agent skill for code-review-swarm - invoke with $agent-code-review-swarm.