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 monkilabs/opencastle --skill linear-task-managementgit clone --depth 1 https://github.com/monkilabs/opencastleWrote 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/monkilabs/opencastle/linear-task-management)<a href="https://agentmods.dev/skills/monkilabs/opencastle/linear-task-management"><img src="https://agentmods.dev/badge/skills/monkilabs/opencastle/linear-task-management/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/monkilabs/opencastle/linear-task-management"><img src="https://agentmods.dev/badge/skills/monkilabs/opencastle/linear-task-management.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.00043 | $0.00491 |
| Opus 5.5 | $0.00017 | $0.00196 |
| Sonnet 5.5 | $0.00009 | $0.00098 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
linear-task-management 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 11d 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.
What it actually says
Task Management with Linear
Team, workflow states and labels: .opencastle/project/linear-config.md. Docs: https://linear.app/docs/mcp
The MCP server
Linear's own remote server (https://mcp.linear.app/mcp), signed in with OAuth — each teammate as themselves, so issue history shows who did what. It finds, creates and updates issues, projects and comments, and lists teams, cycles, statuses and labels. Tool names change between server versions: read the tool list the server offers instead of assuming a name.
Gotchas
- Look up, don't guess. Read the team's statuses and labels from the server before setting them, and record the ones the team uses in
linear-config.md. - Blockers go in a comment on the issue, not in the description — the description is the spec.
- Treat a create as successful only if it returns an issue ID (
TAS-42) — verify before delegating. - GitHub integration auto-transitions on PR events (push → In Progress, review → In Review, merge → Done), configured in Settings → Team → Pull request automation. Link by putting
TAS-123in the branch or PR title. - On resume, re-read every issue status before acting; a stale local view causes double work.
Conventions
Verb-first titles mapping to intent: Add schema: priceRange to place, Migrate DB: add price_range, Update query: include priceRange, Implement UI: PriceRangeFilter.
Priority: P1 blocks other tasks / critical path, P2 core feature on critical path, P3 parallelizable support work, P4 docs and polish.
Flow Backlog → Todo → In Progress → In Review → Done → Cancelled. Every description carries Objective, Files (partition), Acceptance Criteria, Dependencies (#TAS-XX). Group related issues under a Linear project.
Untracked bug: search first; if absent create [Bug] <symptom> with bug + domain labels, P1–P4 plus rationale, and acceptance steps.
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.
- 11d ago Changed · -2 lines · -11 tokens per session 2345899bb1df
- 12d ago First seen · 33 lines · 54 tokens per session scan A 7464ebdd9d6a
linear-task-management is a skill published in the GitHub repository monkilabs/opencastle (80 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 491 once invoked, about $0.0002 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-10-04.
Other skills, from other repositories
jira-ticket-builder
Turns rough input into structured Jira work. Two modes — single-ticket mode turns a bug description, meeting notes, Slack thread, incident writeup, or a few sentences into one fully-structured Jira ticket; decomposition mode turns a rough requirements doc or product brief with multiple asks and open questions into…
task-forest
Maintains a repo-local task forest or task DAG for the current workspace. Use when the user asks to initialize or update a task forest, close a session, summarize evolving project work, align a request with a global goal, track progress/history/deviations/todos, save or apply a task proposal, or export the…
work-report-expert
A writing guide for workplace summaries and presentations, including annual reviews, performance reports, project updates, job-promotion speeches, weekly reports, and monthly reports. It uses clear conclusions, evidence, and the STAR method, which explains a Situation, Task, Action, and Result.
workflow-discovery
Rank workflow candidates using observed repositories, skills, engineering activity and recurring user requests.
product-architect
Complete product development system with 80 agents and 36 frameworks. Use when the user wants to build a product, write a PRD, plan an MVP or roadmap, design an app, research a market or check whether a feature already exists or is novel, do competitive analysis, run a security audit, build a financial model, plan…
using-todo
Use when an Agent needs to capture, find, update, finish, cancel, or reopen durable deferred work in LWC.