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 OpenHands/extensions --skill linear-triagegit clone --depth 1 https://github.com/OpenHands/extensionsWrote 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/openhands/extensions/linear-triage)<a href="https://agentmods.dev/skills/openhands/extensions/linear-triage"><img src="https://agentmods.dev/badge/skills/openhands/extensions/linear-triage/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/openhands/extensions/linear-triage"><img src="https://agentmods.dev/badge/skills/openhands/extensions/linear-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 73 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00055 | $0.00779 |
| Opus 5.5 | $0.00022 | $0.00312 |
| Sonnet 5.5 | $0.00011 | $0.00156 |
| Haiku 4.5 | $0.00006 | $0.00078 |
Grade A, and why
linear-triage scanned grade A with 1 finding 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 14d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X POST "${OPENHANDS_HOST}/api/automation/v1/preset/prompt" \ How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Linear Issue Triage Automation
Set up an automation that triages new Linear issues — classifying, labeling, and suggesting owners automatically.
Prerequisites
Required integration
- Linear MCP must be installed in Settings → MCP.
Information to collect
Ask the user for:
- Teams/projects — which Linear teams or projects should be triaged (e.g.
Engineering,Support) - Label taxonomy — what labels are used for classification? (e.g.
bug,feature,support,chore) - Priority conventions — how does the team use priority levels? Any mapping rules?
- Auto-apply or suggest — should the automation apply labels/priority/assignee directly, or post a triage comment with suggestions for human approval?
- Duplicate detection — should it search for and flag potential duplicate issues?
Setup Workflow
Step 1 — Verify Linear MCP access
Confirm the Linear MCP integration is working:
Use the Linear MCP to list recent issues for one of the target teams.
If it fails, tell the user to install the Linear MCP integration first.
Step 2 — Determine trigger type
Event-based (recommended if publicly reachable):
Check <RUNTIME_SERVICES> for deployment reachability. If public, recommend an event trigger on Linear Issue create events.
Cron-based (local/private deployments): Poll for recently created issues on a schedule (e.g. every 5 minutes).
Step 3 — Build the triage prompt
Construct a prompt that includes:
- Target teams/projects
- Label taxonomy and classification rules
- Priority mapping conventions
- Whether to auto-apply or suggest
- Duplicate detection preference
Step 4 — Create the automation
Set OPENHANDS_HOST and AUTH_HEADER for the request below:
- OpenHands Cloud or Enterprise - a
<HOST>value is in your system prompt: use it asOPENHANDS_HOST, withAUTH_HEADER="Authorization: Bearer $OPENHANDS_API_KEY" - Local Agent Canvas - an Automation backend is listed in
<RUNTIME_SERVICES>: use itsurl_from_agentasOPENHANDS_HOST, withAUTH_HEADER="X-Session-API-Key: $OPENHANDS_AUTOMATION_API_KEY"
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 14d ago Changed 7168190ad33f
- 1mo ago First seen · 94 lines · 55 tokens per session scan A 4a6dfb4a604c
linear-triage is a skill published in the GitHub repository OpenHands/extensions (167 stars, last pushed today), licensed MIT. It adds 55 tokens to every session and 779 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
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…