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.
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.
git 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/plugins/davila7/claude-code-templates/linear-tickets)<a href="https://agentmods.dev/plugins/davila7/claude-code-templates/linear-tickets"><img src="https://agentmods.dev/badge/plugins/davila7/claude-code-templates/linear-tickets/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/plugins/davila7/claude-code-templates/linear-tickets"><img src="https://agentmods.dev/badge/plugins/davila7/claude-code-templates/linear-tickets.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
linear-tickets 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.
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"name": "linear-tickets",
"version": "0.1.0",
"description": "Your Linear tickets in a side pane, with their status and a chart of how you are progressing: tickets grouped by state (in progress, todo, backlog, done), a stacked status bar, a bar chart of tickets closed per day over the last two weeks and, when your tickets sit in a cycle, that cycle's scope and completed burn-up. Read-only; it polls Linear's GraphQL API. /linear opens it. Needs a Linear API key.",
"author": {
"name": "claude-code-templates",
"url": "https://www.aitmpl.com"
},
"repository": "https://github.com/davila7/claude-code-templates",
"license": "MIT",
"keywords": [
"mod",
"function-hooks",
"integrations",
"linear",
"tickets",
"ui",
"chart"
],
"userConfig": {
"linearApiKey": {
"type": "string",
"title": "Linear API key",
"description": "A Linear personal API key (Linear, Settings, Security & access); with none set the mod does nothing. It only reads issues and cycles",
"default": "",
"sensitive": true
},
"assignee": {
"type": "string",
"title": "Whose tickets",
"description": "me lists tickets assigned to you; anyone lists everyone's (narrow it with teamKey or project)",
"default": "me",
"options": [
"me",
"anyone"
]
},
"teamKey": {
"type": "string",
"title": "Team key",
"description": "Only this team's tickets, by its key (the CLA of CLA-143); empty for every team",
"default": ""
},
"project": {
"type": "string",
"title": "Project name contains",
"description": "Only tickets of Linear projects whose name contains this text (case-insensitive); empty for all",
"default": ""
},
"days": {
"type": "number",
"title": "Days of history",
"description": "How far back the done list and the closed-per-day chart reach (7-60)",
"default": 14
},
"pollSeconWhat 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 8f33b28d9d75
- 14d ago First seen · 76 lines scan A 2158b4f3a7fd
linear-tickets is a plugin published in the GitHub repository davila7/claude-code-templates (32,670 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-02.
Other plugins, from other repositories
team-kit
A team's shared Claude Code setup: an onboarding skill and a read-only reviewer for the shared configuration.
commander-hub marketplace
Plugin marketplace listing 1 plugin: commander.
commander
Guided AI PM for Claude Code, running on The Fable Method — 12 enforceable gates so any model produces Fable-shaped results. 84 plugin skills (click-first /ccc- workflows, incl. /ccc-codex for the Codex CLI), 22 specialist sub-agents (architect, reviewer, debugger, designer, security-auditor…), 30 lifecycle hooks × 51.
bounty-board
Turns your repo's tech debt into an aging bounty economy. A SessionStart hook scans tracked files and prices each TODO/FIXME/HACK/skip as a wanted-poster bounty whose XP grows with its git-blame age, injects the top 3 as opportunistic side quests, and, via a PostToolUse hook, verifies and pays out bounties that…
roadmap
Product management, roadmap analysis, and solution architecture with multi-agent orchestration.
g-forge
Educated, enforced project management for AI development - a PM layer, parallel implementation waves, and a git-hook commit gate that can't be skipped. Make any model ship like a senior team.