e2e-validate

A command that checks results from earlier end-to-end tests without running those tests again. End-to-end tests check a complete workflow from input to final output.

In plain words
What is it for?
Use it to inspect saved outputs for YouTube, audio, web pages, documents, downloads, crawled sites, and batch operations.
Why use it?
It gives a quick inventory and validation of existing test artifacts instead of spending time repeating the test run.

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/enablement-engineering/gobbler/e2e-validate
Clone the repo
git clone --depth 1 https://github.com/Enablement-Engineering/gobbler

Made for: Claude Code.

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 2,220 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.02220
Opus 5 $0.00000 $0.01110
Sonnet 5 $0.00000 $0.00444
Haiku 4.5 $0.00000 $0.00222

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

Security

Grade A, and why

e2e-validate 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 2d 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/e2e-validate.md · 372 lines

How it starts

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

E2E Validate - Test Output Validation

Validate existing e2e test outputs without re-running tests.

Time: ~1 minute Requirements: None Purpose: Quick validation of test outputs from previous e2e runs


Phase 1: Locate Test Outputs

Find Test Output Directory

Check for existing test outputs:

ls -lR /tmp/gobbler_e2e_tests/

Expected Directory Structure

/tmp/gobbler_e2e_tests/
├── youtube/           # YouTube transcripts
├── audio/             # Audio transcriptions
├── webpages/          # Web scraping outputs
├── documents/         # Document conversions
├── downloads/         # Downloaded videos
├── crawled/           # Crawled sites
└── batch/
    ├── audio/         # Batch audio results
    ├── documents/     # Batch document results
    ├── webpages/      # Batch webpage results
    └── playlist/      # Playlist batch results

Report Output Inventory

# E2E Validate - Output Inventory

## Output Directory: /tmp/gobbler_e2e_tests/

Found directories:
- youtube/: [X files]
- audio/: [X files]
- webpages/: [X files]
- documents/: [X files]
- downloads/: [X files]
- crawled/: [X files/dirs]
- batch/audio/: [X files]
- batch/documents/: [X files]
- batch/webpages/: [X files]
- batch/playlist/: [X files]

Total files found: [X]

If no outputs found: Report no test outputs to validate


Phase 2: Validation Checks

For Each Markdown File (.md)

Run comprehensive validation:

1. YAML Frontmatter Validation

Check structure:

  • File starts with ---
  • Contains closing ---
  • Valid YAML syntax (parse without errors)

Check required fields:

  • title field present
  • source field present
  • timestamp or created_at field present
  • tool_used or similar metadata present

Parse and validate:

import yaml

with open(file_path) as f:
    content = f.read()

# Extract frontmatter
if content.startswith('---'):
    parts = content.split('---', 2)
    if len(parts) >= 3:
        frontmatter_text = parts[1]
        try:
            metadata = yaml.safe_load(frontmatter_text)
            # Validate required fields
            assert 'title' in metadata
            assert 'source' in metadata
            # etc.
        except Exception as e:
            # Report parsing error

Read the full file on GitHub · 372 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.

  1. 2d ago First seen · 372 lines · 0 tokens per session scan A aae3dd7955f2

Subscribe to this mod's changes

e2e-validate is a command published in the GitHub repository Enablement-Engineering/gobbler (4 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,220 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.