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 nesszer/linear-cli --skill linear-apigit clone --depth 1 https://github.com/nesszer/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/nesszer/linear-cli/linear-api)<a href="https://agentmods.dev/skills/nesszer/linear-cli/linear-api"><img src="https://agentmods.dev/badge/skills/nesszer/linear-cli/linear-api/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/nesszer/linear-cli/linear-api"><img src="https://agentmods.dev/badge/skills/nesszer/linear-cli/linear-api.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.00025 | $0.00237 |
| Opus 5.5 | $0.00010 | $0.00095 |
| Sonnet 5.5 | $0.00005 | $0.00047 |
| Haiku 4.5 | $0.00003 | $0.00024 |
Grade A, and why
linear-api 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.
What it actually says
Raw GraphQL API
# Run a query
linear-cli api query '{ viewer { id name email } }'
# Query with variables
linear-cli api query -v teamId=abc '{ team(id: $teamId) { name } }'
# Run a mutation
linear-cli api mutate -v title="Bug" '
mutation($title: String!) {
issueCreate(input: { title: $title, teamId: "..." }) {
issue { id identifier }
}
}
'
# Pipe query from file
cat query.graphql | linear-cli api query -
Flags
| Flag | Purpose |
|---|---|
-v key=val |
GraphQL variables |
--output json |
JSON output |
--compact |
Compact JSON |
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.
- 1mo ago First seen · 40 lines · 25 tokens per session scan A 52991399b535
linear-api is a skill published in the GitHub repository nesszer/linear-cli (138 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 237 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
saga-orchestration
Implement saga patterns for distributed transactions and cross-aggregate workflows. Use this skill when implementing distributed transactions across microservices where 2PC is unavailable, designing compensating actions for failed order workflows that span inventory, payment, and shipping services, building…
platform-lightning-app-coordinate
Build complete Salesforce Lightning Experience applications from natural language descriptions. Use this skill when a user requests a "complete app", "Lightning app", "business solution", "management system", or describes a scenario requiring multiple interconnected Salesforce components (objects, fields, pages, tabs…
service-agentforce-channel-configure
Wires an existing, active Agentforce agent to a channel by resolving a fallback queue, setting up inbound routing (either PATCH SessionHandlerId on the MessagingChannel, or an inbound RoutingFlow for Voice/Email), and optionally configuring outbound escalation. Use when the user wants to add a channel to an existing…
commerce-app-migrate
Migrate an Adobe Commerce App Builder project from the Integration Starter Kit or Checkout Starter Kit to the new App Management approach. Run from the root of the App Builder project to be migrated. Pass --auto to skip confirmation prompts (suitable for CI or batch use) — auto mode prints a summary of all Q&A…
full-stack-orchestration-full-stack-feature
Coordinate database, backend, frontend, testing, and deployment work for a complete feature. Use when implementing changes that span multiple application layers.
multi-platform-apps-multi-platform
Build and deploy the same feature consistently across web, mobile, and desktop platforms using API-first architecture and parallel implementation strategies.