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 skills add joa23/linear-cli --skill link-depsgit 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/link-deps)<a href="https://agentmods.dev/skills/joa23/linear-cli/link-deps"><img src="https://agentmods.dev/badge/skills/joa23/linear-cli/link-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/link-deps"><img src="https://agentmods.dev/badge/skills/joa23/linear-cli/link-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.00029 | $0.02170 |
| Opus 5.5 | $0.00012 | $0.00868 |
| Sonnet 5.5 | $0.00006 | $0.00434 |
| Haiku 4.5 | $0.00003 | $0.00217 |
Grade A, and why
link-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 — 357 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Link Deps Skill - Dependency Discovery
You are an expert at discovering hidden dependencies between issues and establishing proper work order.
When to Use
Use this skill when:
- You have many unconnected issues in your backlog
- Work order is unclear because dependencies aren't explicit
- Issues reference each other in descriptions but aren't formally linked
- You need to understand prerequisite work before starting a feature
The Problem
Teams often have hundreds of issues without explicit dependencies. This makes it hard to:
- Know what to work on next
- Understand what blocks what
- Plan sprints effectively
- Parallelize work
Common scenario: You have 500 backlog issues but don't realize ENG-123 must be done before ENG-456 can start.
The Solution
Use search with dependency filters to discover relationships:
# 1. Find issues with similar keywords that might be related
linear search "authentication" --team ENG --format full
# 2. Check if any already have dependencies
linear search "authentication" --has-dependencies --team ENG
# 3. Look for blocked work to identify bottlenecks
linear search --has-blockers --state "Todo" --team ENG
# 4. Find circular dependencies that need fixing
linear search --has-circular-deps --team ENG
Discovery Process
1. Identify Related Work
Search for issues by theme:
# Find all auth-related work
linear search "auth" --team ENG --format full
# Find all database-related work
linear search "database" --team ENG --format full
# Find all API-related work
linear search "API" --team ENG --format full
2. Analyze for Dependencies
For each group, look for:
- Foundation work - Core infrastructure others depend on
- Feature work - Built on top of foundation
- Follow-up work - Enhancements after initial feature
3. Establish Relationships
Link dependencies using --blocked-by:
# Feature depends on foundation
linear issues update ENG-456 --blocked-by ENG-123
# Follow-up depends on feature
linear issues update ENG-789 --blocked-by ENG-456
# Multiple dependencies
linear issues update ENG-500 --blocked-by ENG-123,ENG-456
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 · 357 lines · 29 tokens per session scan A a04edfe91fac
link-deps is a skill published in the GitHub repository joa23/linear-cli (145 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 2,170 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…