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-awarenessnpx skills add eveld/claude --skill linear-awarenessgit clone --depth 1 https://github.com/eveld/claudeWrote 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/eveld/claude/linear-awareness)<a href="https://agentmods.dev/skills/eveld/claude/linear-awareness"><img src="https://agentmods.dev/badge/skills/eveld/claude/linear-awareness.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.00024 | $0.00972 |
| Opus 5 | $0.00012 | $0.00486 |
| Sonnet 5 | $0.00005 | $0.00194 |
| Haiku 4.5 | $0.00002 | $0.00097 |
Grade A, and why
linear-awareness 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Linear Skills Guide
You have specialized Linear issue management skills. Use these for structured ticket workflows during debugging investigations.
Decision Tree
Skills vs Agents
Simple issue fetch or update? → Use Linear skills
linear-issues- Fetch, list, search issues (single linearis command)linear-update- Update issue, add comments- Example: "Get details for ENG-1234"
- Use when: Single issue, straightforward query/update
Complex investigation requiring analysis? → Use Task tool with Linear agents (conserves context)
linear-locator- Find issues by criteria, save to /tmplinear-analyzer- Extract debugging context, parse technical detailslinear-pattern-finder- Find patterns across issues, detect recurring problems- Use when: Multi-issue analysis, pattern detection, trend analysis
When to Use Which Agent
Just need to find issues broadly?
→ Use linear-locator agent only
- Lists/searches issues by team, label, state, text
- Saves filtered results to /tmp
- Example: "Find all FileB-related issues across teams"
Investigating single issue for debugging?
→ Use linear-locator + linear-analyzer agents
- Locator: Find issue and related issues
- Analyzer: Extract error messages, URLs, technical details
- Example: "Analyze ENG-1234 for debugging context"
Need to find patterns or recurring problems?
→ Use all three: linear-locator + linear-analyzer + linear-pattern-finder
- Locator: Fetch issues by criteria
- Analyzer: Parse each issue for technical details
- Pattern-finder: Correlate across issues, find recurring themes, temporal trends
- Example: "Find recurring VCS permission errors across last 2 months"
Adding debugging findings to a ticket?
→ Use linear-update skill
- Better than: Running raw
linearis comments createcommands - Example: "Add root cause analysis to ENG-1234"
Updating issue status after investigation?
→ Use linear-update skill
- Includes: status, priority, labels updates
- Example: "Mark ENG-1234 as In Progress"
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 · 120 lines · 24 tokens per session scan A 90d9e3f6d852
linear-awareness is a skill published in the GitHub repository eveld/claude (10 stars, last pushed 7mo ago), licensed MIT. It adds 24 tokens to every session and 972 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
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.
specification-writing
Write the full patent specification from claims and invention disclosure. Use when user says "撰写说明书", "write specification", "写说明书", "patent description", or wants to draft the complete patent specification.
training-check
Interactively monitor training metrics from the current Codex session, periodically checking WandB or fallback logs for NaN, divergence, plateaus, and broken runs.