linear-continue-testing

linear-continue-testing is a command for Claude Code from greyhaven-ai/sygaldry. It costs 0 tokens per session (558 once invoked), scanned A, original, MIT.

A command for continuing software testing, finding gaps in test coverage, adding tests, checking for unreliable tests, and recording results in Linear.

In plain words
What is it for?
Use it to run the test suite, measure coverage, identify missing scenarios, write regression and integration tests, check for flaky tests, and update the related Linear work.
Why use it?
It helps reveal untested behaviour and makes sure new tests cover normal cases, errors, edge cases, and past bugs.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/greyhaven-ai/sygaldry/linear-continue-testing
Clone the repo
git clone --depth 1 https://github.com/greyhaven-ai/sygaldry

Made for: Claude Code.

Wrote 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.

agentmods badge for linear-continue-testing

README.md
[![agentmods](https://agentmods.dev/badge/commands/greyhaven-ai/sygaldry/linear-continue-testing.svg)](https://agentmods.dev/commands/greyhaven-ai/sygaldry/linear-continue-testing)
Your own site
<a href="https://agentmods.dev/commands/greyhaven-ai/sygaldry/linear-continue-testing"><img src="https://agentmods.dev/badge/commands/greyhaven-ai/sygaldry/linear-continue-testing.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 558 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00558
Opus 5 $0.00000 $0.00279
Sonnet 5 $0.00000 $0.00112
Haiku 4.5 $0.00000 $0.00056

Measured 4d ago against content hash 62d2606dcd85, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

linear-continue-testing 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 4d 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.

.claude/commands/linear-continue-testing.md · 73 lines

What it actually says

Continue testing for the following: $ARGUMENTS

  1. Assess current test coverage:

    • Run existing tests: pytest -v (or project-specific test command)
    • Generate coverage report: pytest --cov=contextframe --cov-report=html
    • Review coverage gaps in key files
    • Check for TODO/FIXME in test files
  2. Identify missing test scenarios:

    • Unit tests for individual functions/methods
    • Integration tests for feature workflows
    • Edge cases from issue comments or discovered bugs
    • Error handling and validation tests
    • Performance/load tests if applicable
  3. Write comprehensive tests:

    • Start with failing tests for uncovered scenarios
    • Test happy paths and error conditions
    • Include boundary value tests
    • Add regression tests for any bugs found
    • Document test purpose and expected behavior
  4. Validate test quality:

    • Ensure tests fail when code is broken
    • Check test isolation (no order dependencies)
    • Verify test data cleanup
    • Run tests multiple times for flakiness
    • Review test readability and maintenance
  5. Update Linear tracking:

    • Comment with test coverage improvements
    • List any discovered issues or concerns
    • Update issue status if testing complete
    • Create new issues for bugs found during testing
  6. Generate test summary:

    • Coverage before/after metrics
    • New test scenarios added
    • Any failing tests that need fixes
    • Recommendations for additional testing

Quality is ensured through comprehensive testing. Continue systematically to catch issues before users do.

Take a deep breath in, count 1... 2... 3... and breathe out. You are now centered. Don't hold back. Give it your all.

Changes

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.

  1. 4d ago First seen · 73 lines · 0 tokens per session scan A 62d2606dcd85

Subscribe to this mod's changes

linear-continue-testing 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 558 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.