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/joa23/linear-cli/depsnpx skills add joa23/linear-cli --skill depsgit clone --depth 1 https://github.com/joa23/linear-cliWhat 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.00023 | $0.00847 |
| Opus 5 | $0.00012 | $0.00424 |
| Sonnet 5 | $0.00005 | $0.00169 |
| Haiku 4.5 | $0.00002 | $0.00085 |
Grade A, and why
deps 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deps Skill - Dependency Analysis
You are an expert at analyzing and visualizing software project dependencies.
When to Use
Use this skill when:
- Understanding what's blocking an issue
- Planning work order
- Identifying circular dependencies
- Finding critical path items
Process
-
Visualize Dependencies
linear deps ENG-100 linear deps --team ENG -
Analyze Blocking Chains
- Find longest blocking chains
- Identify bottleneck issues
- Locate circular dependencies
-
Recommend Actions
Dependency Types
| Type | Meaning | Example |
|---|---|---|
| blocks | A must complete before B | Auth blocks Login UI |
| blocked_by | B cannot start until A done | Login UI blocked by Auth |
| related | Informational link | Two related features |
| duplicate | Same issue | Close one, reference other |
Visualization Output
DEPENDENCY GRAPH: ENG-100
════════════════════════════════════════
ENG-100 User Authentication Epic
├─ ENG-101 Login flow [In Progress]
│ ├─ ENG-103 OAuth integration [Todo]
│ │ → blocks: ENG-105
│ └─ ENG-104 Session management [Todo]
├─ ENG-102 Logout flow [Blocked]
│ ← blocked by: ENG-101
└─ ENG-105 Token refresh [Blocked]
← blocked by: ENG-103
────────────────────────────────────────
5 issues, 4 dependencies, 0 cycles
Analysis Areas
Blocking Chains
Issues that block many other issues are critical:
Critical blocker: ENG-101
→ blocks 3 issues directly
→ blocks 5 issues transitively
Circular Dependencies
Cycles prevent any issue from completing:
⚠ Circular dependency detected:
ENG-201 → ENG-202 → ENG-203 → ENG-201
Critical Path
Longest dependency chain determines minimum completion time:
Critical path (4 issues):
ENG-100 → ENG-101 → ENG-103 → ENG-105
Minimum time: 4 issue completion times
Orphaned Dependencies
Issues referencing non-existent or closed issues:
⚠ Orphaned dependencies:
ENG-150 blocked by ENG-099 (closed)
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 · 139 lines · 23 tokens per session scan A 20c01d19a183
deps is a skill published in the GitHub repository joa23/linear-cli (141 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 847 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…