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 dgalarza/claude-code-workflows --skill linear-implementgit clone --depth 1 https://github.com/dgalarza/claude-code-workflowsWrote 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/dgalarza/claude-code-workflows/linear-implement)<a href="https://agentmods.dev/skills/dgalarza/claude-code-workflows/linear-implement"><img src="https://agentmods.dev/badge/skills/dgalarza/claude-code-workflows/linear-implement/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/dgalarza/claude-code-workflows/linear-implement"><img src="https://agentmods.dev/badge/skills/dgalarza/claude-code-workflows/linear-implement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Memory Poisoning · line 183 Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
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.00080 | $0.03983 |
| Opus 5.5 | $0.00032 | $0.01593 |
| Sonnet 5.5 | $0.00016 | $0.00797 |
| Haiku 4.5 | $0.00008 | $0.00398 |
Grade A, and why
linear-implement 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.
How it starts
The opening of the file, as written. The whole thing — 617 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Linear Issue Implementation
Overview
This skill provides a comprehensive workflow for implementing Linear issues with professional software engineering practices. It automates the entire development lifecycle from issue analysis through PR creation, ensuring quality through test-driven development, parallel code reviews, and systematic validation.
When to Use This Skill
Use this skill when:
- User provides a Linear issue ID (format:
TRA-9,DEV-123, etc.) - User requests implementation of a Linear issue
- User wants a structured TDD approach with code review
- User needs automated workflow from issue to PR
Examples:
- "Implement TRA-142"
- "Help me build the feature in DEV-89"
- "Work on Linear issue ABC-456"
Core Workflow
The skill follows a 14-step process:
- Fetch Linear Issue - Retrieve complete issue details via Linear MCP
- Gather Additional Context - Search Obsidian, Sentry, and GitHub for related information
- Move to In Progress - Update issue status to indicate active work
- Create Feature Branch - Use Linear's suggested git branch naming
- Analyze & Plan - Break down requirements and create implementation plan
- Save to Memory - Store plan in memory graph for tracking
- Review Plan - Present plan for user confirmation
- TDD Implementation - Invoke
tdd-workflowskill for test-driven development - Parallel Code Reviews - Invoke
parallel-code-reviewskill for comprehensive analysis - Address Feedback - Invoke
code-review-implementerskill to systematically fix issues - Validation - Ensure all tests and linters pass
- Logical Commits - Create meaningful commit history
- Create PR - Generate comprehensive pull request with Linear linking
- Final Verification - Confirm CI/CD pipeline and Linear integration
Workflow Implementation Details
Step 1: Fetch Linear Issue Details
Retrieve the complete issue using Linear MCP tools:
mcp__linear__get_issue(id: <issue-id>)
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 · 617 lines · 80 tokens per session scan A b75ec0123b62
linear-implement is a skill published in the GitHub repository dgalarza/claude-code-workflows (62 stars, last pushed 3d ago), licensed MIT. It adds 80 tokens to every session and 3,983 once invoked, about $0.0003 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 skills, from other repositories
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
gh-issue
Size-audit, write, and split BanyanDB issues that somebody else or an automated TDD workflow can implement. Use whenever the user asks to file or revise an issue, decide whether an issue is too large, make an issue TDD-ready, turn a design into tickets, or split an umbrella into executable leaves. Do not draft or file…
implement-feature
Implement an approved feature plan with fresh-context slices, TDD, revision-bound evidence, and PR-ready output.
product
Consolidated Galyarder Framework Product intelligence bundle.
ring:implementing-tasks
Implementing a single planned task (Task N.M.T) end-to-end: selects the right backend agent by language and service type, drives one TDD RED->GREEN turn, then verifies coverage, lint, license headers, runtime, and delivery before handoff. Runs as Gate 0 before ring:reviewing-code. Use to drive ONE task inside an…
create-issues
Creates GitHub issues following test-driven development principles and proper labeling conventions. This skill should be used when the user asks to "create an issue", "file a bug", or needs to document new requirements, epics, or PR-scoped tasks.