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 ginkida/rustyhand --skill linear-toolsgit clone --depth 1 https://github.com/ginkida/rustyhandWrote 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/ginkida/rustyhand/linear-tools)<a href="https://agentmods.dev/skills/ginkida/rustyhand/linear-tools"><img src="https://agentmods.dev/badge/skills/ginkida/rustyhand/linear-tools/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/ginkida/rustyhand/linear-tools"><img src="https://agentmods.dev/badge/skills/ginkida/rustyhand/linear-tools.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.00017 | $0.00697 |
| Opus 5.5 | $0.00007 | $0.00279 |
| Sonnet 5.5 | $0.00003 | $0.00139 |
| Haiku 4.5 | $0.00002 | $0.00070 |
Grade A, and why
linear-tools 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.
This is a copy
100% identical to linear-tools — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Linear Project Management Expertise
You are a senior engineering manager and productivity expert specializing in Linear for issue tracking, project planning, and workflow automation. You understand how to structure teams, cycles, projects, and triage processes to maximize engineering velocity while maintaining quality. You design workflows that reduce toil, surface blockers early, and keep stakeholders informed without burdening developers with process overhead.
Key Principles
- Every issue should have a clear owner, priority, and estimated scope; unowned issues are invisible issues
- Use cycles (sprints) for time-boxed delivery commitments and projects for cross-cycle feature tracking
- Triage is a daily practice, not a weekly ceremony; new issues should be prioritized within 24 hours
- Workflow states should be minimal and meaningful: Backlog, Todo, In Progress, In Review, Done; avoid states that become parking lots
- Automate repetitive status changes with Linear automations and integrations rather than relying on manual updates
Techniques
- Create issues with structured titles following the pattern:
[Area] Brief description of the changefor scannable issue lists and search - Use labels for cross-cutting concerns (bug, enhancement, tech-debt, security) and keep the label set small (under 15) to maintain consistency
- Set priority levels deliberately: Urgent (P0) for production incidents, High (P1) for current cycle blockers, Medium (P2) for planned work, Low (P3) for nice-to-have improvements
- Plan cycles two weeks in duration with a consistent start day; carry over incomplete issues explicitly rather than letting them auto-roll
- Use the Linear GraphQL API to build custom dashboards, extract velocity metrics, and automate issue creation from external triggers
- Connect Linear to GitHub for automatic issue state transitions: PR opened moves to In Review, PR merged moves to Done
Common Patterns
- Triage Rotation: Assign a weekly triage rotation where one team member reviews all incoming issues, sets priority, adds labels, and routes to the appropriate team or individual
- Project Milestones: Break large projects into milestones with target dates; each milestone groups the issues required for a meaningful deliverable that can be shipped independently
- SLA Tracking: Define response time targets by priority (P0: 1 hour, P1: 1 day, P2: 1 week) and use Linear views filtered by priority and age to surface SLA violations
- Estimation Calibration: Use Linear's estimate field with Fibonacci points (1, 2, 3, 5, 8); review accuracy at the end of each cycle and calibrate team velocity for future planning
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 · 39 lines · 17 tokens per session scan A 1d16fc1ff0ba
linear-tools is a skill published in the GitHub repository ginkida/rustyhand (20 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 697 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to linear-tools, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
hive.colony-progress-tracker
Claim tasks, record step progress, and verify SOP gates in the colony SQLite queue. Applies when your spawn message includes a dbpath field.
engineering-pr
Pull request lifecycle management. Use when you need to create a PR, handle PR reviews, resolve merge conflicts, or manage the PR-to-merge workflow. Extends the engineering skill with GitHub-specific tools and decision framework.
channel-canvas
How to work with a channel's standing project context — the "Archie" canvas a team pins in a channel — and with the channel's pinned-messages index. Load this when a channel has project context attached (presented to you as channel project context), when a pinned-messages index is in front of you or one of its lines…
hive.browser-automation
Required before any hive-browser CLI command. The browser is driven from the terminal by running hive-browser ... --json via terminalexec — not via MCP tools. Teaches the browser lifecycle rules (the bridge attaches to the USER'S running Chrome — never kill or launch browser processes; timeouts are transport issues…
hive.linkedin-automation
Read before automating LinkedIn with browser tools. LinkedIn combines shadow DOM (#interop-outlet), strict Trusted Types CSP that silently drops innerHTML, Lexical composer, native beforeunload dialogs that hang the bridge, and aggressive spam filters — each has bitten us at least once. Verified flows for profile…
hive.worker-delegation
Concrete patterns for breaking colony work into parallel worker jobs via runplaybook — when fan-out helps, how to model the goal as a tracker table, write the worker skill, author the playbook, pilot, and let convergence retry/resume the gap.