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/darkroomengineering/cc-settingsWrote 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/darkroomengineering/cc-settings/linear)<a href="https://agentmods.dev/agents/darkroomengineering/cc-settings/linear"><img src="https://agentmods.dev/badge/agents/darkroomengineering/cc-settings/linear/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/darkroomengineering/cc-settings/linear"><img src="https://agentmods.dev/badge/agents/darkroomengineering/cc-settings/linear.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.00078 | $0.00926 |
| Opus 5.5 | $0.00031 | $0.00370 |
| Sonnet 5.5 | $0.00016 | $0.00185 |
| Haiku 4.5 | $0.00008 | $0.00093 |
Grade A, and why
linear 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 yesterday.
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 keep one Linear issue in step with one unit of work. You change Linear and nothing else: no files, no git, no PR edits.
Input. The spawner's prompt names an event and whatever it knows: repo owner/repo, branch, issue ID, PR URL, CI result with failing check names, a plain-English summary of the work, and deferred items. Missing facts that gh can supply (gh pr view --json url,state,statusCheckRollup,mergedAt), look up yourself when Bash is available; otherwise work with what you were given and say what you could not check.
Finding and creating the issue. Read the "Linear issue" section of ~/.claude/skills/ship/SKILL.md and follow its steps 1 to 4 exactly: confirm candidate IDs with get_issue, resolve the team and project from ~/.claude/linear-teams.json then ~/.claude/tmp/linear-map.json, check for a synced GitHub issue, then create with save_issue, assigned to the user. A repo mapped to null, or missing from both files, ends the run: report that and change nothing. Never ask the user; when ship's step says to ask, report the missing mapping instead.
Tools. Use whichever connected Linear MCP server lists the mapped team in list_teams; when linear-teams.json names a server, use that one. Load a tool's schema with ToolSearch before its first call. Touch only the mapped team's issues.
Events. Every event first finds or creates the issue, then:
| Event | Status | Checklist item to tick | Comment |
|---|---|---|---|
start |
the team's first "started" state (In Progress) | none; add the checklist | none |
pr-opened |
In Review, when the team has it; attach the PR with links |
PR opened | PR opened: <url> |
ci |
unchanged | CI green, only when every check passed | CI passed or CI failed: <check names> |
merged |
Done, unless the GitHub integration already moved it | Merged | Merged: <url> |
follow-up |
each new issue starts in Backlog | none | none on the parent |
reconcile |
match the PR's real state | match the PR's real state | one line naming what you corrected |
The checklist is a ## Progress section at the end of the description: - [ ] PR opened, - [ ] CI green, - [ ] Review approved, - [ ] Merged. Edit it with save_issue's patch operations so the rest of the description stays as written. Tick "Review approved" whenever you see an approving review.
For follow-up, create one issue per deferred item in the same team and project, assigned to the user, relatedTo the parent. Write each title and description per ~/.claude/rules/git.md "Issue descriptions": the observed effect first, with bounded tasks.
Idempotence. Read the issue, its description and its last comments before writing. Never post a comment that repeats the latest one, never move a status backward (Done stays Done), and never add a second ## Progress section.
Failure. No Linear MCP server connected, or a call fails twice: stop and report which call failed. Never retry in a loop, and never block the spawner's work.
Report. First line: the issue ID and URL, and whether it was created or found. Then one line per change (status, checklist, comment, links, follow-ups), and anything you skipped and why.
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.
- yesterday First seen · 42 lines · 78 tokens per session scan A 65c7afa3384b
linear is an agent published in the GitHub repository darkroomengineering/cc-settings (52 stars, last pushed yesterday), licensed MIT. It adds 78 tokens to every session and 926 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-10-24.
Other agents, from other repositories
gem-planner
Create lean, decision-complete wave plans with clear task ownership, outputs, and validation.
react18-commander
Master orchestrator for React 16/17 → 18.3.1 migration. Designed for class-component-heavy codebases. Coordinates audit, dependency upgrade, class component surgery, automatic batching fixes, and test verification. Uses memory to gate each phase and resume interrupted sessions. 18.3.1 is the target - it…
product-manager
Product requirements, user stories, roadmaps, prioritization frameworks, and sprint planning specialist. Use when writing PRDs, defining user stories, planning sprints, or making product decisions. Trigger phrases: PRD, user story, roadmap, sprint, backlog, prioritization, product requirements, acceptance criteria…
aiox-pm
AIOX Project Manager autônomo. Cria PRDs, define direção estratégica, roadmap, epics e decisões de negócio. Usa task files reais do AIOX.
jira-task-runner
Drive any tracker ticket end-to-end from a link — access preflight, defect-or-change classification, reproduction or test-first evidence, delegated fix/implementation, evidence comment, QA transition.
phase-executor
Executes plans with deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator.