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/elnora-ai/elnora-linear/linear-workspacenpx skills add Elnora-AI/elnora-linear --skill linear-workspacegit clone --depth 1 https://github.com/Elnora-AI/elnora-linearWrote 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/elnora-ai/elnora-linear/linear-workspace)<a href="https://agentmods.dev/skills/elnora-ai/elnora-linear/linear-workspace"><img src="https://agentmods.dev/badge/skills/elnora-ai/elnora-linear/linear-workspace.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.00126 | $0.01919 |
| Opus 5 | $0.00063 | $0.00959 |
| Sonnet 5 | $0.00025 | $0.00384 |
| Haiku 4.5 | $0.00013 | $0.00192 |
Grade A, and why
linear-workspace 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 6d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Linear Workspace
Router for Linear work. Dispatches to specialized agents or slash commands rather than running things inline.
Dispatch table
| Intent | Action |
|---|---|
| Create one issue from a description | Agent: linear-issue-creator |
| Create issues from a URL / article / design | Agent: linear-url-to-issues |
| Review one existing issue (clarity, completeness) | Agent: linear-issue-reviewer |
| Edit one existing issue (state, assignee, comment, close, …) | Agent: linear-issue-updater |
| Search / list issues | Slash command: /linear-search |
| List your own issues | Slash command: /linear-my-issues |
| Apply the same change to many issues | Slash command: /linear-bulk |
| Find + handle stale issues | Slash command: /linear-cleanup |
| Refresh reference data from Linear | Slash command: /linear-sync |
| Run the curator (collect signals from external sources) | Slash command: /linear-curator-run |
For parallel work (e.g. 5 issues from 5 URLs), dispatch multiple agents in a single message — that's why they exist.
First-run install
/plugin marketplace add Elnora-AI/elnora-linearthen/plugin install linear-workspace@elnora-linear- Make sure the
elnora-linearCLI is on your PATH:npm install -g @elnora-ai/linear - On your first Linear command, you'll be prompted for your Linear API key (get one at https://linear.app/settings/api). It's saved to
~/.config/elnora-linear/.env(mode 0600). - Populate the reference files:
/linear-sync(runselnora-linear sync all— fetches teams, projects, users, workflows in one batch).
Reference files
The plugin reads user-specific config from ~/.config/elnora-linear/ by default (override via LINEAR_REFERENCES_DIR):
teams.json,projects.json,users.json,workflows.json— populated by/linear-syncslack.json,repos.json,signal-sources.json,label-policy.json— populated manually (schemas inschemas/, examples inreferences/*.example.json)
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.
- 6d ago First seen · 114 lines · 126 tokens per session scan A 9cc0cdf1c620
linear-workspace is a skill published in the GitHub repository Elnora-AI/elnora-linear (7 stars, last pushed yesterday), licensed Apache-2.0. It adds 126 tokens to every session and 1,919 once invoked, about $0.0006 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
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.
implement-issue
Take a GitHub issue from planning to PR, resumable across clarification waits.
plan-backlog
Turn a vision document into a curated backlog of proposed epics and one-PR issues.
review-health
Audit any repository's structural health and file the findings as proposed epics and one-PR issues.
beads-schema
Beads (bd CLI) reference — issue types, statuses, priorities, dependencies, and common commands.
gitlab-group
GitLab group operations via API. ALWAYS use this skill when user wants to: (1) list/view groups, (2) create/update/delete groups, (3) manage group members, (4) list subgroups or group projects, (5) share projects with groups.