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 kubiyabot/skill --skill linear-skillgit clone --depth 1 https://github.com/kubiyabot/skillWrote 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/kubiyabot/skill/linear-skill)<a href="https://agentmods.dev/skills/kubiyabot/skill/linear-skill"><img src="https://agentmods.dev/badge/skills/kubiyabot/skill/linear-skill/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/kubiyabot/skill/linear-skill"><img src="https://agentmods.dev/badge/skills/kubiyabot/skill/linear-skill.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.00008 | $0.00983 |
| Opus 5.5 | $0.00003 | $0.00393 |
| Sonnet 5.5 | $0.00002 | $0.00197 |
| Haiku 4.5 | $0.00001 | $0.00098 |
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 1mo 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Linear Skill
Issue tracking and project management through the Linear GraphQL API.
Installation
skill install ./examples/wasm-skills/linear-skill
Configuration
skill config linear --set LINEAR_API_KEY=lin_api_xxxxx
Get your API key from Linear Settings > API > Personal API keys.
Tools
list-issues
List issues with filtering options.
Parameters:
team(optional, string): Team key or IDproject(optional, string): Project name or IDstatus(optional, string): Status: backlog, todo, in_progress, done, cancelledassignee(optional, string): Assignee email or IDlimit(optional, number): Maximum results (default: 50)
Example:
skill run linear list-issues --team ENG --status in_progress
get-issue
Get detailed information about a specific issue.
Parameters:
id(required, string): Issue ID (e.g., ENG-123)
Example:
skill run linear get-issue --id ENG-123
create-issue
Create a new issue.
Parameters:
title(required, string): Issue titleteam(required, string): Team keydescription(optional, string): Issue descriptionpriority(optional, number): Priority (0=None, 1=Urgent, 2=High, 3=Medium, 4=Low)assignee(optional, string): Assignee emaillabels(optional, string): Comma-separated label namesestimate(optional, number): Point estimate
Example:
skill run linear create-issue --title "Fix login bug" --team ENG --priority 2
update-issue
Update an existing issue.
Parameters:
id(required, string): Issue IDtitle(optional, string): New titledescription(optional, string): New descriptionstatus(optional, string): New statuspriority(optional, number): New priorityestimate(optional, number): Point estimate
Example:
skill run linear update-issue --id ENG-123 --priority 1 --status in_progress
add-comment
Add a comment to an issue.
Parameters:
issue_id(required, string): Issue IDbody(required, string): Comment content (Markdown supported)
What ships with it
3 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.
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.
- 1mo ago First seen · 168 lines · 8 tokens per session scan A abb495812c31
linear is a skill published in the GitHub repository kubiyabot/skill (19 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 8 tokens to every session and 983 once invoked, about $0.0000 per session on Opus 5.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-09-03.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…