Claude Code Templates is a command-line tool and catalogue for configuring Anthropic’s Claude Code with agents, commands, settings, hooks, integrations, skills, and project templates. Developers use it to browse and install reusable components for their coding workflows. The catalogue includes many of these Claude Code components.
Borrowing it
Nothing to install: this file belongs to davila7/claude-code-templates. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/davila7/claude-code-templates/main/.claude/agents/linear-tracker.mdgit clone --depth 1 https://github.com/davila7/claude-code-templatesWrote 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/agents/davila7/claude-code-templates/linear-tracker)<a href="https://agentmods.dev/agents/davila7/claude-code-templates/linear-tracker"><img src="https://agentmods.dev/badge/agents/davila7/claude-code-templates/linear-tracker/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/agents/davila7/claude-code-templates/linear-tracker"><img src="https://agentmods.dev/badge/agents/davila7/claude-code-templates/linear-tracker.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.00031 | $0.00503 |
| Opus 5.5 | $0.00012 | $0.00201 |
| Sonnet 5.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 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.
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.
- 1mo 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 (32,814 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 503 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-30.
Other agents, from other repositories
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…
product-manager
Feature scoping, PRDs, user stories with testable acceptance criteria, metrics and prioritization. Use to turn an idea into a buildable spec or to order a backlog.
project-planner
Use this agent when you need to create a comprehensive development task list from a Product Requirements Document (PRD). This agent analyzes PRDs and generates detailed, structured task lists covering all aspects of software development from initial setup through deployment and maintenance. Examples: Context: User…
prd-writer
Use this agent when you need to create a comprehensive Product Requirements Document (PRD) for a software project or feature. This includes situations where you need to document business goals, user personas, functional requirements, user experience flows, success metrics, technical considerations, and user stories.…
product-manager
Product management and value maximization expert. Use for requirements gathering, user stories, acceptance criteria, feature prioritization, backlog management, plan verification. Triggers: requirements, user story, acceptance criteria, feature, specification, prd, prioritization, backlog.
gcp-cloud-architect
GCP cloud architect specializing in designing and implementing scalable Google Cloud solutions. Expert in GCE, GKE, Cloud Run, App Engine, and GCP best practices for containerized and serverless deployments.