A command for running a detailed quality check of a Tilt MCP integration. Tilt is a development tool that manages and monitors services while they run.

Use it to inspect system status, list and describe resources, read logs, test filters and pagination, and document failures.

It helps reveal missing data, broken filters, pagination problems, incomplete details, and other integration bugs.

How alleneubank/tilt-mcp configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to alleneubank/tilt-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/alleneubank/tilt-mcp/main/.claude/commands/tilt-qa.md

Clone the repo

git clone --depth 1 https://github.com/alleneubank/tilt-mcp

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/alleneubank/tilt-mcp/tilt-qa/github.svg)](https://agentmods.dev/commands/alleneubank/tilt-mcp/tilt-qa)

Your own site

<a href="https://agentmods.dev/commands/alleneubank/tilt-mcp/tilt-qa"><img src="https://agentmods.dev/badge/commands/alleneubank/tilt-mcp/tilt-qa/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/alleneubank/tilt-mcp/tilt-qa"><img src="https://agentmods.dev/badge/commands/alleneubank/tilt-mcp/tilt-qa.svg" alt="Reviewed on agentmods" width="80" 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 1,144 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.01144
Opus 5	$0.00000	$0.00572
Sonnet 5	$0.00000	$0.00229
Haiku 4.5	$0.00000	$0.00114

Measured 8d ago against content hash d20a32e7c852, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

tilt-qa 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 8d 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/tilt-qa.md · 141 lines

How it starts

The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Tilt QA Demonstration and Bug Report

Run a comprehensive quality assurance session for the Tilt MCP integration, testing all tools and identifying bugs.

Instructions

Execute the following QA workflow systematically, documenting results at each step:

Phase 1: Discovery and Initial Status

Check Overall Status
- Use tilt_status to get system-wide status
- Document: resources count, overall state, any warnings
- ❌ Bug check: Missing data? Incorrect formatting? Errors?

Phase 2: Resource Operations

List Resources
- Use tilt_get_resources with different filters:
  - All resources (default)
  - Filter by status (ok, error, pending, building)
  - With verbose output
  - With pagination (limit/offset)
- Document: resources found, their states, response times
- ❌ Bug check: Pagination issues? Filtering broken? Missing fields?
Describe Resources
- Use tilt_describe_resource on 2-3 different resources
- Test with different resource types if available
- Document: detail level, completeness, formatting
- ❌ Bug check: Invalid resource names handling? Incomplete data? Errors?

Phase 3: Logs and Monitoring

Read Logs
- Use tilt_logs (plain-text output) with various options:
  - Default tail (100 lines)
  - Different tail line counts (50, 200)
  - Filter by source (build, runtime, all)
  - Filter by level (warn, error) — note: filters Tilt system messages only
  - Client-side search:
    - Substring match (case-sensitive and case-insensitive)
    - Regex with flags (e.g., im), ensure invalid regex throws clear error
- Document: log output, filtering effectiveness, search behavior, performance
- ❌ Bug check: Missing logs? Incorrect filtering? Search not applied? Timeout issues? Errors not descriptive for bad regex?

Phase 4: Resource Control

Trigger Updates
- Use tilt_trigger on a resource (choose one safely)
- Document: trigger response, resource state change
- ❌ Bug check: Trigger fails? No feedback? State inconsistency?

Read the full file on GitHub · 141 lines

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.

8d ago First seen · 141 lines · 0 tokens per session scan A d20a32e7c852

Subscribe to this mod's changes

tilt-qa is a command published in the GitHub repository alleneubank/tilt-mcp (5 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,144 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-31.

Testing

verify

Run repository verification using the verification-loop skill.

cloudnative-co/claude-code-starter-kit · 9 tokens

qa-changes

This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…

OpenHands/extensions · 63 tokens

tilt-mcp: Command for Claude Code