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 eveld/claude --skill linear-updategit clone --depth 1 https://github.com/eveld/claudeWrote 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/eveld/claude/linear-update)<a href="https://agentmods.dev/skills/eveld/claude/linear-update"><img src="https://agentmods.dev/badge/skills/eveld/claude/linear-update/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/eveld/claude/linear-update"><img src="https://agentmods.dev/badge/skills/eveld/claude/linear-update.svg" alt="Reviewed on agentmods" width="80" 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.00027 | $0.01226 |
| Opus 5.5 | $0.00011 | $0.00490 |
| Sonnet 5.5 | $0.00005 | $0.00245 |
| Haiku 4.5 | $0.00003 | $0.00123 |
Grade A, and why
linear-update 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.
How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Linear Issue
Update Linear issues with debugging findings, status changes, and investigation notes.
When to Use
- Adding debugging findings as comments
- Updating issue status after investigation
- Adding labels for categorization
- Changing priority based on severity
- Recording root cause analysis
Pre-flight Checks
Authentication
# Check linearis is available and authenticated
linearis --version 2>/dev/null || {
echo "linearis CLI not installed"
exit 1
}
linearis issues list --limit 1 >/dev/null 2>&1 || {
echo "Not authenticated to Linear"
exit 1
}
Common Commands
1. Add Comment
# Add single-line comment
linearis comments create ENG-1234 --body "Root cause identified: database connection pool exhausted"
# Add multi-line comment with heredoc
linearis comments create ENG-1234 --body "$(cat <<'EOF'
## Investigation Findings
**Root Cause**: Database connection pool exhausted
**Evidence**:
- GCP logs show "connection refused" errors starting at 10:30 UTC
- Kubernetes events show 1/3 pods in CrashLoopBackOff
- Pod describe shows max_connections reached
**Timeline**:
- 10:28 UTC: Traffic spike to 3x normal
- 10:30 UTC: First connection errors
- 10:32 UTC: Pod restarts begin
**Recommendation**: Increase database connection pool limit from 100 to 250
EOF
)"
2. Update Issue Status
# Change state to "In Progress"
linearis issues update ENG-1234 --state "In Progress"
# Change state to "Done"
linearis issues update ENG-1234 --state "Done"
# Common states: "Backlog", "Todo", "In Progress", "In Review", "Done", "Canceled"
3. Update Priority
# Set priority (1 = Urgent, 2 = High, 3 = Medium, 4 = Low)
linearis issues update ENG-1234 --priority 1
# Lower priority after resolution
linearis issues update ENG-1234 --priority 4
4. Add Labels
# Add labels (comma-separated)
linearis issues update ENG-1234 --labels "bug,production,database"
# Add labels (adding mode - default)
linearis issues update ENG-1234 --labels "investigating" --label-by adding
# Replace all labels (overwriting mode)
linearis issues update ENG-1234 --labels "resolved,production" --label-by overwriting
# Clear all labels
linearis issues update ENG-1234 --clear-labels
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 · 178 lines · 27 tokens per session scan A a97347740190
linear-update is a skill published in the GitHub repository eveld/claude (10 stars, last pushed 8mo ago), licensed MIT. It adds 27 tokens to every session and 1,226 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-31.
Other skills, from other repositories
bug-triage
Re-evaluate open bugs — priority vs severity, assign to sprints, surface systemic trends. Run when the count grows.
event-planner
Event planning with timelines, budgets, vendor coordination, logistics checklists, and post-event evaluation. Use when organizing conferences, workshops, galas, or corporate events.
monitoring-observability
OpenTelemetry, structured logging, distributed tracing, alerting, and dashboards. Use when instrumenting services, designing logs/traces/metrics, defining SLOs and alerts, or debugging production behavior from telemetry.
hr-talent
HR and talent management expertise for talent acquisition, performance management, compensation strategy, organizational design, culture building, succession planning, and D&I programs. Use when hiring, managing performance, designing organizations, or building culture.
leadership
Executive leadership expertise for decision-making, change management, crisis management, stakeholder management, team building, and organizational leadership. Use when leading teams, managing change, navigating crises, or developing leadership skills.
product-management
Product management expertise for product strategy, roadmap planning, feature prioritization (RICE, ICE, MoSCoW), customer research, A/B testing, product analytics, and product-market fit. Use when building product roadmaps, prioritizing features, or defining product strategy.