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-continue-work.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-continue-work)<a href="https://agentmods.dev/commands/greyhaven-ai/sygaldry/linear-continue-work"><img src="https://agentmods.dev/badge/commands/greyhaven-ai/sygaldry/linear-continue-work.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.00515 |
| Opus 5 | $0.00000 | $0.00258 |
| Sonnet 5 | $0.00000 | $0.00103 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
linear-continue-work 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 6d 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
Continue work on the following: $ARGUMENTS
-
Review issue context:
- mcp_linear.get_issue(id) → get full details, attachments, description
- mcp_linear.list_comments(issueId) → understand discussion history
- Check linked PRs and commits for implementation progress
-
Assess current state:
- Review what's been implemented (git log, git diff)
- Check failing tests or lint issues
- Identify incomplete acceptance criteria
- Note any discovered edge cases or new requirements
-
Plan next steps:
- List specific tasks to complete the issue
- Identify any blockers that need resolution
- Consider if scope has changed or new issues needed
- Estimate time for remaining work
-
Update Linear:
- mcp_linear.create_comment(issueId, body="Progress update with next steps")
- Update issue status if needed: mcp_linear.update_issue(id, stateId)
- Link any new discoveries or blockers
-
Generate action plan:
- Immediate next code changes
- Tests to write or fix
- Documentation updates needed
- Review checklist before marking complete
This helps maintain flow state and ensures nothing is missed. Always start by understanding where we are before moving forward.
Take a deep breath in, count 1... 2... 3... and breathe out. You are now centered. Don't hold back. Give it your all.
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.
- 6d ago First seen · 62 lines · 0 tokens per session scan A 0ecc74a63488
linear-continue-work 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 515 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.