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 initializ/forge --skill lineargit clone --depth 1 https://github.com/initializ/forgeWrote 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/initializ/forge/linear)<a href="https://agentmods.dev/skills/initializ/forge/linear"><img src="https://agentmods.dev/badge/skills/initializ/forge/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/initializ/forge/linear"><img src="https://agentmods.dev/badge/skills/initializ/forge/linear.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 118 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00022 | $0.02002 |
| Opus 5.5 | $0.00009 | $0.00801 |
| Sonnet 5.5 | $0.00004 | $0.00400 |
| Haiku 4.5 | $0.00002 | $0.00200 |
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 2mo 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 How it starts
The opening of the file, as written. The whole thing — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Linear Skill
You can read, search, and update Linear issues, list workflow states, and post comments. Use this skill as the entry point for ticket-driven workflows — turn ENG-123 into a structured payload, transition state, comment on progress.
When to use this skill
- The user references a Linear issue by identifier (
ENG-123,OPS-7, etc.). - The user asks for "my tickets" / "open issues" / "what's assigned to me".
- An automation needs to mark work started, post a PR link as a comment, or move a ticket through workflow states.
Issue identifier format
Linear identifiers look like <TEAM_KEY>-<NUMBER> — ENG-123, OPS-7. They are not GraphQL UUIDs. The Linear API accepts both forms on issue(id:), so always pass the human identifier the user gave you. Never invent or normalise identifiers — use them verbatim.
State transition pattern (hard rule)
You MUST call linear_get_workflow_states first and use the resolved id when calling linear_update_issue_state. State IDs are per-team UUIDs; state names like "Todo" or "In Progress" are not portable across teams and cannot be passed to linear_update_issue_state directly.
Workflow:
linear_get_issueto find the issue'steam.id.linear_get_workflow_stateswith thatteam_idto enumerate the team's states.- Pick the state by matching its
name(case-insensitive) ortype(unstarted,started,completed,canceled,triage,backlog). linear_update_issue_statewith the issue identifier and the resolvedstate_id.
Commenting etiquette
Post a comment when:
- Work has been picked up (one comment, e.g.
"Working on this."). - A pull request has been opened (one comment with the PR URL).
- Work is blocked and the user should know.
- Work is complete (one comment summarising what shipped).
Do not chatter. Post no more than one comment per agent action. Do not narrate intermediate tool calls, file edits, or reasoning into Linear comments — the channel-side conversation is the place for that. Comments are durable artifacts on the ticket; treat them like git commit messages, not Slack messages.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- scripts/common.sh 1.6 KB runs code
- scripts/linear-add-comment.sh 1.8 KB runs code
- scripts/linear-get-issue.sh 1.1 KB runs code
- scripts/linear-get-workflow-states.sh 1.1 KB runs code
- scripts/linear-list-my-issues.sh 1.7 KB runs code
- scripts/linear-search-issues.sh 3.3 KB runs code
- scripts/linear-update-issue-state.sh 1.4 KB runs code
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.
- 2mo ago First seen · 216 lines · 22 tokens per session scan A d57357527e48
linear is a skill published in the GitHub repository initializ/forge (235 stars, last pushed yesterday), licensed Apache-2.0. It adds 22 tokens to every session and 2,002 once invoked, about $0.0001 per session on Opus 5.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-08-30.
linear compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| linearinitializ/forge | Skill | 235 | yesterday | Apache-2.0 | A | 22 | Claude Code, Codex |
| Linearwrsmith108/linear-claude-skill | Skill | 140 | 3mo ago | MIT | A | 32 | Claude Code |
| Linear Automationclaude-office-skills/skills | Skill | 563 | 9mo ago | MIT | A | 18 | Claude Code, Codex |
| github-project-managementruvnet/RuView | Skill | 103k | yesterday | MIT | A | 25 | Claude Code |
| quality-looptrpc-group/trpc-agent-go | Skill | 1.9k | yesterday | Apache-2.0 | A | 32 | Claude Code, Codex |
| mcportertrpc-group/trpc-agent-go | Skill | 1.9k | yesterday | Apache-2.0 | A | 51 | Claude Code, Codex |
| plan_routetrpc-group/trpc-agent-go | Skill | 1.9k | yesterday | Apache-2.0 | A | 17 | Claude Code, Codex |