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/nesszer/linear-cli/linear-webhooksnpx skills add nesszer/linear-cli --skill linear-webhooksgit clone --depth 1 https://github.com/nesszer/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.00026 | $0.00340 |
| Opus 5 | $0.00013 | $0.00170 |
| Sonnet 5 | $0.00005 | $0.00068 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
linear-webhooks 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.
What it actually says
Webhooks
# List all webhooks
linear-cli wh list
# Create a webhook
linear-cli wh create https://example.com/hook --events Issue
# Get webhook details
linear-cli wh get WEBHOOK_ID
# Update a webhook
linear-cli wh update WEBHOOK_ID --url https://new-url.com
# Delete a webhook
linear-cli wh delete WEBHOOK_ID --force
# Rotate signing secret
linear-cli wh rotate-secret WEBHOOK_ID
# Listen for events locally (dev/testing)
linear-cli wh listen --port 9000
linear-cli wh listen --port 9000 --secret SIGNING_SECRET
Subcommands
| Command | Purpose |
|---|---|
list |
List all webhooks |
get |
View webhook details |
create |
Create webhook |
update |
Update webhook |
delete |
Delete webhook |
rotate-secret |
Rotate signing secret |
listen |
Local event listener with HMAC verification |
Flags
| Flag | Purpose |
|---|---|
--events TYPE |
Event types to subscribe |
--port N |
Local listener port |
--secret KEY |
HMAC signing secret |
--output json |
JSON output |
Exit Codes
0=Success, 1=Error, 2=Not found, 3=Auth error
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 · 57 lines · 26 tokens per session scan A dad7a5355c22
linear-webhooks is a skill published in the GitHub repository nesszer/linear-cli (133 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 340 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…