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/fortiumpartners/ensemble/managing-linear-issuesnpx skills add FortiumPartners/ensemble --skill managing-linear-issuesgit clone --depth 1 https://github.com/FortiumPartners/ensembleWrote 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/fortiumpartners/ensemble/managing-linear-issues)<a href="https://agentmods.dev/skills/fortiumpartners/ensemble/managing-linear-issues"><img src="https://agentmods.dev/badge/skills/fortiumpartners/ensemble/managing-linear-issues.svg" alt="Measured on agentmods" height="20"></a>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.00046 | $0.02378 |
| Opus 5 | $0.00023 | $0.01189 |
| Sonnet 5 | $0.00009 | $0.00476 |
| Haiku 4.5 | $0.00005 | $0.00238 |
Grade A, and why
managing-linear-issues 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 — 350 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Linear Integration Skill
Purpose: Issue management for Linear.app using Linearis CLI with JSON output optimized for LLM agents.
Tool: Linearis CLI - npm package linearis
Table of Contents
- Prerequisites
- Decision Tree
- Quick Command Reference
- Pattern Recognition - Auto-Invocation
- Workflow Examples
- Error Handling
- Authentication Strategy
- JSON Output Handling
Prerequisites
Verify Installation
# Check CLI installed
linearis --version
Authentication (Priority Order)
IMPORTANT: Always check for project-specific credentials first. Different projects may use different Linear workspaces.
-
Project .env (PREFERRED - project-specific):
# Check project .env for LINEAR_API_KEY grep LINEAR_API_KEY .env # Run commands with project token export LINEAR_API_TOKEN="$(grep LINEAR_API_KEY .env | cut -d= -f2)" linearis teams list -
Environment Variable (session override):
export LINEAR_API_TOKEN="lin_api_xxx"
Running Commands with Project Credentials
# Inline token from project .env (recommended)
LINEAR_API_TOKEN=$(grep LINEAR_API_KEY .env | cut -d= -f2) linearis <command>
# Or export for session
export LINEAR_API_TOKEN=$(grep LINEAR_API_KEY .env | cut -d= -f2)
linearis <command>
Decision Tree
Issue Operations
User wants to...
├── View issue details
│ └── linearis issues read <ISSUE-ID>
├── Create new issue
│ └── linearis issues create "Title" --team <Team> [options]
├── Update existing issue
│ └── linearis issues update <ISSUE-ID> [--state|--assignee|--priority]
├── Search issues
│ └── linearis issues search "query" [--team|--limit]
├── List recent issues
│ └── linearis issues list [--limit N] [--team Name]
└── Delete issue (soft)
└── linearis issues update <ISSUE-ID> --trashed
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 · 350 lines · 46 tokens per session scan A 4cd6831d82f4
managing-linear-issues is a skill published in the GitHub repository FortiumPartners/ensemble (11 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 2,378 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
saas-auth
Implement production-ready authentication for SaaS applications including email/password, OAuth social login, session management, and security best practices. This skill covers the complete auth lifecycle from signup through password recovery.
saas-payments
Implement production-ready payment processing with Stripe including one-time payments, recurring subscriptions, customer portal, metered billing, and webhook handling. This skill covers the complete billing lifecycle from checkout through subscription management.
saas-analytics
Implement product analytics for understanding user behavior, tracking key metrics, and making data-driven decisions. Covers event tracking, user identification, cohort analysis, and integration with analytics platforms like PostHog, Mixpanel, or custom solutions.
saas-onboarding
Implement effective user onboarding flows that drive activation and reduce churn. Covers setup wizards, progress checklists, contextual tooltips, and tracking of key activation milestones. Focus on getting users to their "aha moment" quickly.
saas-billing
Implement subscription lifecycle management, plan enforcement, usage tracking, and billing operations. Covers trial periods, plan changes, quota enforcement, and subscription status synchronization with payment providers.
saas-email
Implement reliable transactional email delivery for SaaS applications including templating, queuing, delivery tracking, and provider abstraction. Covers common email types: welcome, verification, password reset, notifications, and invoices.