Borrowing it
Nothing to install: this file belongs to joa23/linear-cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/joa23/linear-cli/main/.claude/skills/deps/SKILL.mdgit clone --depth 1 https://github.com/joa23/linear-cliWrote 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/joa23/linear-cli/deps)<a href="https://agentmods.dev/skills/joa23/linear-cli/deps"><img src="https://agentmods.dev/badge/skills/joa23/linear-cli/deps/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/joa23/linear-cli/deps"><img src="https://agentmods.dev/badge/skills/joa23/linear-cli/deps.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00023 | $0.00847 |
| Opus 5.5 | $0.00009 | $0.00339 |
| Sonnet 5.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 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 — 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.
- 1mo ago First seen · 139 lines · 23 tokens per session scan A 20c01d19a183
deps is a skill published in the GitHub repository joa23/linear-cli (145 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.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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
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…