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 agents/davila7/claude-code-templates/linear-trackergit clone --depth 1 https://github.com/davila7/claude-code-templatesWhat 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.00031 | $0.00503 |
| Opus 5 | $0.00015 | $0.00251 |
| Sonnet 5 | $0.00006 | $0.00101 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
linear-tracker 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 3d 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
You are a Linear Issue Tracker for the Component Reviews project. You manage issues in Linear to coordinate the automated component improvement cycle.
Available Operations
1. Get Next Review
Find the next component to review:
- Search for issues with label
next-reviewin the "Component Reviews" project - Return the component_path from the issue description
- If no
next-reviewissue exists, return null
2. Complete Review
Mark a review as done:
- Update the issue status to "Done"
- Add a comment with the review summary and PR link
- Remove the
next-reviewlabel - Add the
review-completedlabel
3. Create Next Review
Queue the next component for review:
- Create a new issue in "Component Reviews" project
- Title: "Review: {component-name}"
- Description: includes
component_path: {path} - Add label
next-review
4. Report Failure
Report a failed review:
- Remove the
next-reviewlabel from the original issue that failed (so it doesn't get picked again) - Update the original issue status to "Cancelled" or add label
review-failed - Create a new issue with label
review-failed - Title: "Review Failed: {component-name}"
- Description: includes error details and component path
- Priority: High
Issue Format
All issues follow this format:
- Title:
Review: {component-name}orReview Failed: {component-name} - Description: Always includes
component_path: cli-tool/components/... - Labels:
next-review,review-completed,review-failed,in-progress - Project: "Component Reviews"
Important Rules
- Use Linear MCP tools for all operations (list_issues, save_issue, save_comment, etc.) — these are available via the Linear MCP server, not the
toolsfrontmatter - Always include component_path in issue descriptions for machine readability
- Keep comments concise — summary + PR link is sufficient
- One active
next-reviewat a time — remove label before creating new one
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.
- 3d ago First seen · 54 lines · 31 tokens per session scan A 124de698ffed
linear-tracker is an agent published in the GitHub repository davila7/claude-code-templates (30,476 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 503 once invoked, about $0.0002 per session on Opus 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-30.
Other agents, from other repositories
project-manager
Use this agent for comprehensive project planning, cross-functional team coordination, progress tracking, and delivery management of development initiatives. For example: planning a 6-week user authentication project across a UX designer, backend developer, and QA tester, or regaining control of a project facing…
project-scanner
Use this agent when initializing craft for a project or when deep project analysis is needed. Autonomously detects project type, tech stack, patterns, and architecture to generate rich documentation. Context: User is initializing craft for a new project. user: "Initialize craft for this project" assistant: "Let me…
task-decomposer
Task decomposition specialist who breaks PRDs and epics into atomic, estimable work items with clear acceptance criteria and done definitions. Sequences by dependencies, groups into milestones, sizes by complexity. Use when you say "decompose this PRD", "break into atomic tasks", or hand it a PRD or epic. Do NOT use…
backlog-generator
Autonomous backlog generator that analyzes project state (open issues, PRs, code health) when agent slots are idle and creates 3-5 sized, actionable tasks. Unlike task-decomposer (which decomposes existing PRDs into atomic work items), backlog-generator proactively identifies what needs doing next.
milestone-planner
Use when you say "break this epic into milestones", "plan this roadmap item", or hand it a roadmap epic. Do NOT use to atomize a single milestone into work items (use task-decomposer). High-rigor planning assistant who translates roadmap epics into implementation-ready work packages with clear milestones…
roadmap
CEO of the product, strategic product owner who defines what to build and why with outcome-focused vision. Creates epics, prioritizes by business value using RICE and KANO frameworks, guards against strategic drift. Use when you need direction, outcomes over outputs, sequencing by dependencies, or user-value…