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/eveld/claude/linear-issuesnpx skills add eveld/claude --skill linear-issuesgit clone --depth 1 https://github.com/eveld/claudeWhat 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.00033 | $0.01220 |
| Opus 5 | $0.00016 | $0.00610 |
| Sonnet 5 | $0.00007 | $0.00244 |
| Haiku 4.5 | $0.00003 | $0.00122 |
Grade A, and why
linear-issues 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Query Linear Issues
Fetch and view Linear issues to gather context for debugging investigations.
When to Use
- Viewing issue details for debugging context
- Searching for related issues
- Checking issue status and priority
- Reading issue descriptions and comments
- Finding issues by ID or search query
Pre-flight Checks
Authentication
# linearis uses API token from environment or config
# Check if linearis is available
linearis --version 2>/dev/null || {
echo "linearis CLI not installed"
echo "Install: npm install -g linearis"
exit 1
}
# Test authentication (list with limit 1)
linearis issues list --limit 1 >/dev/null 2>&1 || {
echo "Not authenticated to Linear"
echo "Set LINEARIS_API_TOKEN environment variable or use --api-token flag"
exit 1
}
Common Commands
Read Issue Details
# Get issue by ID or identifier
linearis issues read ENG-1234
# Output is JSON - use jq to parse
linearis issues read ENG-1234 | jq '.title'
linearis issues read ENG-1234 | jq '.description'
linearis issues read ENG-1234 | jq '.state.name'
# Full issue details
linearis issues read ENG-1234 | jq '.'
List Issues
# List recent issues (default limit: 25)
linearis issues list
# Limit results
linearis issues list --limit 10
linearis issues list --limit 100
# Save to file for analysis
linearis issues list --limit 50 > /tmp/linear-issues-$(date +%Y%m%d).json
Search Issues
# Search by text query
linearis issues search "api-gateway error"
linearis issues search "production crash"
linearis issues search "kubernetes pod"
# Save search results
linearis issues search "database connection" > /tmp/linear-search-$(date +%Y%m%d).json
Output Format
All linearis commands output JSON. Use jq to parse and extract fields.
Common jq patterns:
# Extract issue title
linearis issues read ENG-1234 | jq -r '.title'
# Extract state
linearis issues read ENG-1234 | jq -r '.state.name'
# Extract assignee
linearis issues read ENG-1234 | jq -r '.assignee.name'
# Extract labels
linearis issues read ENG-1234 | jq -r '.labels[].name'
# Extract priority (0=None, 1=Low, 2=Medium, 3=High, 4=Urgent)
linearis issues read ENG-1234 | jq -r '.priority'
What ships with it
1 file 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.
- 2d ago First seen · 170 lines · 33 tokens per session scan A a0e44c4946a7
linear-issues is a skill published in the GitHub repository eveld/claude (10 stars, last pushed 6mo ago), licensed MIT. It adds 33 tokens to every session and 1,220 once invoked, about $0.0002 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
code-indexing-pipeline
How Infigraph turns source into a graph — adding a language (tree-sitter vs ANTLR grammar-plugin), cross-file call resolution, SCIP compiler-grade enrichment, and file-watch/reindex triage. Use when adding language support, debugging unresolved calls or SCIP import, or triaging stale index/watcher issues.
analysis-subsystems
How Infigraph's multi-repo/group mode and taint analysis work internally — HTTP contract extraction heuristics, cross-service edge linking, combined-graph merge, remote mode, plus taint's line-based tracking and sanitizer heuristic. Use when working on crates/infigraph-core/src/multi/ or src/taint/, or investigating…
review-pr-against-issue
Review one or more PRs against the GitHub issue(s) they claim to fix, including fetching PR branches directly when gh can't reach github.com (e.g. gh is authenticated to an enterprise host instead). Use whenever asked "does this PR fix issue.
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
golden-rss
Use when testing the rss golden build.
omh-code-review
This is a Hermes-native code-review workflow skill.