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 alivirgo/Major-AI-Skills --skill lineargit clone --depth 1 https://github.com/alivirgo/Major-AI-SkillsWrote 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/alivirgo/major-ai-skills/linear)<a href="https://agentmods.dev/skills/alivirgo/major-ai-skills/linear"><img src="https://agentmods.dev/badge/skills/alivirgo/major-ai-skills/linear/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/alivirgo/major-ai-skills/linear"><img src="https://agentmods.dev/badge/skills/alivirgo/major-ai-skills/linear.svg" alt="Reviewed on agentmods" width="80" 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.00028 | $0.01211 |
| Opus 5 | $0.00014 | $0.00606 |
| Sonnet 5 | $0.00006 | $0.00242 |
| Haiku 4.5 | $0.00003 | $0.00121 |
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 10d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Linear Product Issue Tracking AI Skill Guide (Claude)
Overview & Engine Architecture
Linear is a high-speed issue tracker for product/engineering teams with Issues, Projects, Cycles, Initiatives, and Workflow states. Automation uses the Linear GraphQL API, personal API keys / OAuth, and webhooks. Claude operates as a Principal Product Operations Engineer, specializing in issue triage mutations, project roadmap queries, label taxonomies, and idempotent webhook handlers.
Linear Domain & API Stack
┌─────────────────────────────────────────────────────────────┐
│ Linear Architecture │
│ │
│ Product Objects │
│ ├── Teams / Members / Workflow States │
│ ├── Issues / Labels / Comments / Attachments │
│ └── Projects / Cycles / Initiatives │
│ │
│ API │
│ ├── GraphQL endpoint https://api.linear.app/graphql │
│ ├── API Key (Authorization: <key>) │
│ └── Webhooks (issue create/update, comments, ...) │
│ │
│ Client Surfaces │
│ ├── Desktop / Web / Mobile │
│ ├── Slack / GitHub integrations │
│ └── @linear/sdk │
└─────────────────────────────────────────────────────────────┘
Operational Capabilities & Agent Directives
- Team-Scoped Writes: Always resolve
teamIdbeforeissueCreate. - State by Type: Prefer state IDs/types (
started,completed) over hard-coded names when possible. - Idempotent Imports: Key off external IDs in description/attachments or custom fields patterns.
- Rate Limits: Batch thoughtfully; prefer GraphQL selection sets that fetch only needed fields.
- Webhook Verification: Validate signatures when Linear provides signing secrets.
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.
- 10d ago First seen · 139 lines · 28 tokens per session scan A 68a086e2b80a
linear is a skill published in the GitHub repository alivirgo/Major-AI-Skills (1 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 1,211 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
linear
Linear project management — issues, cycles, and projects via GraphQL API.
meeting-scheduler
Schedules meetings with internal and external stakeholders by parsing natural language requests, resolving time zones, checking calendar availability, proposing optimal slots, and managing invitations and RSVPs. Use when the user requests meeting scheduler or provides relevant inputs for this workflow.
Linear
Managing Linear issues, projects, and teams. Use when working with Linear tasks, creating issues, updating status, querying projects, or managing team workflows.
airtable-automation-v2
Airtable Automation via Rube MCP workflow skill. Use this skill when the user needs Automate Airtable tasks via Rube MCP (Composio): records, bases, tables, fields, views. Always search tools first for current schemas and the operator should preserve the upstream workflow, copied support files, and provenance before…
c-linear
Manage Linear issues and projects using the linear CLI. List and filter issues, create new issues, update status, start work on a branch, and create linked pull requests directly from the terminal.
airtable-automation-v3
Airtable Automation via Rube MCP workflow skill. Use this skill when the user needs Automate Airtable tasks via Rube MCP (Composio): records, bases, tables, fields, views. Always search tools first for current schemas and the operator should preserve the upstream workflow, copied support files, and provenance before…