Borrowing it
Nothing to install: this file belongs to greyhaven-ai/sygaldry. 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/greyhaven-ai/sygaldry/main/.claude/commands/linear-retroactive-git.mdgit clone --depth 1 https://github.com/greyhaven-ai/sygaldryWrote 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/commands/greyhaven-ai/sygaldry/linear-retroactive-git)<a href="https://agentmods.dev/commands/greyhaven-ai/sygaldry/linear-retroactive-git"><img src="https://agentmods.dev/badge/commands/greyhaven-ai/sygaldry/linear-retroactive-git.svg" alt="Measured on agentmods" 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.00000 | $0.03369 |
| Opus 5 | $0.00000 | $0.01684 |
| Sonnet 5 | $0.00000 | $0.00674 |
| Haiku 4.5 | $0.00000 | $0.00337 |
Grade A, and why
linear-retroactive-git 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 7d 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 — 441 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze git working state and create comprehensive Linear issues using the Linear MCP
-
Check Linear Context:
- Use
mcp__linear__get_teamto get team info - Use
mcp__linear__list_issue_statusesto get available statuses - Use
mcp__linear__list_issue_labelsto get available labels - Use
mcp__linear__list_projectsto identify relevant project
- Use
-
Search for Related Existing Issues and Projects:
- Use
mcp__linear__list_projectsto find active projects that could organize this work - Check for projects with status != "completed" or "cancelled"
- Use
mcp__linear__list_issuesto find related open issues - Check issue titles and descriptions for relevance
- Determine if changes should be attached to existing issues or projects
- Use
-
Categorize Changes:
- Group by component/module
- Identify change types and map to Linear labels:
- Feature (new functionality)
- Bug (fixes)
- Refactor (code improvements)
- Documentation (docs updates)
- Improvement (enhancements)
- Testing (test additions/updates)
- Technical Debt (cleanup)
- Performance (optimizations)
- Security (security improvements)
- Maintenance (dependency updates, etc.)
-
Create Project and Issue Structure:
For major groups of related changes:
a) Find or Create a Project to organize related work:
// First, check for existing applicable projects const existingProjects = await mcp__linear__list_projects({ teamId: team.id, includeArchived: false }); // Look for active projects that match our work let project = existingProjects.find(p => { const isActive = !p.completedAt && !p.canceledAt && !p.archivedAt; const isRelevant = p.name.includes("Refactor") || p.name.includes("AI Agent") || p.description?.includes("agent") || p.description?.includes("refactor"); return isActive && isRelevant; }); // Only create new project if no suitable one exists if (!project) { project = await mcp__linear__create_project({ name: "Refactor: AI Agent Architecture", teamId: team.id, summary: "Consolidate AI agent system and remove redundant code", description: `## Overview Major refactoring effort to improve the AI agent system by removing redundant code and implementing cleaner patterns. ## Scope - Remove duplicate response models across all agents - Consolidate tool imports - Fix import issues and circular dependencies - Implement proper factory pattern - Clean up unused evaluation files ## Affected Components - Healthcare Agent - Education Agent - Exa Agent - Agent Registry and Factory - Test Suite ## Technical Approach 1. Audit current agent implementations 2. Remove duplicate files 3. Update imports to use centralized tools 4. Ensure all tests pass 5. Update documentation`, targetDate: "2025-07-01" }); } else { console.log(`Using existing project: ${project.name} (${project.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.
- 7d ago First seen · 441 lines · 0 tokens per session scan A c4929003e5df
linear-retroactive-git is a command published in the GitHub repository greyhaven-ai/sygaldry (11 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,369 tokens. 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 commands, from other repositories
gsd:quick
Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents.
backlog-git
Control de versiones para backlogs de proyectos.
company-repo
Gestionar el repositorio Company Savia: crear, conectar, estado, sincronizar. El repositorio compartido de la empresa para conocimiento, mensajería y estado.
gsd:pause-work
Create context handoff when pausing work mid-phase.
gsd:remove-phase
Remove a future phase from roadmap and renumber subsequent phases.
weekly-summary
Generate weekly work summary from git activity.