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/eobarretooo/clawlite/linearnpx skills add eobarretooo/ClawLite --skill lineargit clone --depth 1 https://github.com/eobarretooo/ClawLiteWhat 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.00017 | $0.00441 |
| Opus 5 | $0.00009 | $0.00220 |
| Sonnet 5 | $0.00003 | $0.00088 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
linear 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X POST "$ENDPOINT" \ What it actually says
Linear
Use this skill when the user wants to create, update, search, or triage Linear issues and projects.
Auth
Set LINEAR_API_KEY (from https://linear.app/settings/api).
ENDPOINT="https://api.linear.app/graphql"
HEADERS='-H "Authorization: $LINEAR_API_KEY" -H "Content-Type: application/json"'
Search issues
query {
issues(filter: { state: { name: { eq: "In Progress" } } }, first: 20) {
nodes { id identifier title priority state { name } assignee { name } }
}
}
curl -s -X POST "$ENDPOINT" \
-H "Authorization: $LINEAR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"query":"{ issues(first:20){nodes{id identifier title state{name}}} }"}'
Create an issue
mutation {
issueCreate(input: {
title: "Fix login bug"
description: "Steps to reproduce..."
teamId: "TEAM_ID"
priority: 2
}) {
issue { id identifier url }
}
}
Update issue state
mutation {
issueUpdate(id: "ISSUE_ID", input: { stateId: "STATE_ID" }) {
issue { id state { name } }
}
}
Get teams and states
query { teams { nodes { id name states { nodes { id name } } } } }
Safety notes
- Always retrieve
teamIdandstateIdbefore mutations. - Priority values: 0=No priority, 1=Urgent, 2=High, 3=Medium, 4=Low.
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 · 73 lines · 17 tokens per session scan A e29254ce76b9
linear is a skill published in the GitHub repository eobarretooo/ClawLite (49 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 441 once invoked, about $0.0001 per session on Opus 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-08-30.
Other skills, from other repositories
linear
Search, read, create, and update the user's Linear issues, projects, and comments through per-user OAuth.
dispatch
Use when a task file exists in .hyperflow/tasks/ and workers need dispatching. Fans out parallel workers under per-batch Reviewers, runs a final integration review, and commits per sub-task. Endpoint of the auto-chain — no auto-deploy. Trigger with /hyperflow:dispatch, "run the plan", "execute the task", "build it"…
retro-enforcement
Ensure retrospectives happen on schedule and that their action items are tracked in GitHub Issues — not markdown checklists.
commonly
You are a member of a Commonly workspace — a shared space where humans and AI agents from any origin collaborate in pods (chat rooms with memory). Use this whenever you are connected to Commonly via the commonly MCP tools: to read what's happening, post, remember things across sessions, react, DM other agents, and…
oma-pm
Product manager that decomposes requirements into actionable tasks with priorities and dependencies. Use for planning, requirements, specification, scope, prioritization, task breakdown, and ISO 21500, ISO 31000, or ISO 38500-aligned planning recommendations.
cross-machine-coordination
Enables squad agents on different machines to share work via git-based task queuing.