agentmods.dev

frogger: Command for Claude Code

.claude/commands/trace-validate.md

trace-validate is a command for Claude Code from ultra-ai-dle/frogger. It costs 0 tokens per session (565 once invoked), scanned A, original, MIT.

A project-specific command that checks whether trace data remains valid as it moves from browser workers through storage, AI analysis, and rendering. A trace is a recorded sequence of program steps and their variables.

In plain words
What is it for?
Use it to validate trace schemas, compare variable type information, check merged trace entries, and verify worker message payloads.
Why use it?
It finds mismatched fields, missing variables, broken merges, and conflicting errors at the boundaries between parts of the application. It reports problems with file and line references.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

This is ultra-ai-dle/frogger's own configuration. It tells Claude Code how to work on frogger itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything frogger configures →

not rated 8repo 6mo ago A scan 0 tokens original MIT
View source ↗ ultra-ai-dle/frogger frogger-six.vercel.app
Reuse

Borrowing it

Nothing to install: this file belongs to ultra-ai-dle/frogger. 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/ultra-ai-dle/frogger/develop/.claude/commands/trace-validate.md
Clone the repo
git clone --depth 1 https://github.com/ultra-ai-dle/frogger

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 trace-validate

README.md
[![agentmods](https://agentmods.dev/badge/commands/ultra-ai-dle/frogger/trace-validate/github.svg)](https://agentmods.dev/commands/ultra-ai-dle/frogger/trace-validate)
Your own site
<a href="https://agentmods.dev/commands/ultra-ai-dle/frogger/trace-validate"><img src="https://agentmods.dev/badge/commands/ultra-ai-dle/frogger/trace-validate/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.

agentmods 80×15 button for trace-validate

Your own site · 80×15
<a href="https://agentmods.dev/commands/ultra-ai-dle/frogger/trace-validate"><img src="https://agentmods.dev/badge/commands/ultra-ai-dle/frogger/trace-validate.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 565 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00565
Opus 5.5 $0.00000 $0.00226
Sonnet 5.5 $0.00000 $0.00113
Haiku 4.5 $0.00000 $0.00056

Measured 27d ago against content hash 066cfee7774c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

trace-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 27d 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/trace-validate.md · 36 lines

What it actually says

/trace-validate — Trace 스키마 + 병합 무결성 검증

목적

Pyodide Worker → Store → AI → Renderer 경계에서 trace 데이터가 올바르게 흐르는지 검증한다.

입력

  • $ARGUMENTS — (선택) 검증 범위 지정 (예: schema, merge, vartypes). 미지정 시 전체 검증.

실행 절차

  1. RawTraceStep 스키마 검증 (schema):

    • src/types/prova.ts의 RawTraceStep 정의를 읽는다.
    • Worker 파일(public/worker/pyodide.worker.js, public/worker/js.worker.js)에서 postMessage로 보내는 데이터 구조가 RawTraceStep과 일치하는지 확인한다.
    • 필수 필드: step, line, vars, scope, parent_frames, runtimeError
    • scope는 { func: string, depth: number } 형태여야 한다.

  2. varTypes 합집합 검증 (vartypes):

    • Worker에서 생성하는 varTypes의 키가 실제 rawTrace[].vars의 키 합집합과 일치하는지 로직을 추적한다.
    • /api/analyze에서 varTypes를 받아 var_mapping.var_name을 생성할 때, 존재하지 않는 변수명을 참조하는 경로가 없는지 확인한다.

  3. mergedTrace 병합 무결성 (merge):

    • src/features/trace/merge.ts의 병합 로직을 읽는다.
    • rawTrace.length !== annotatedChunk.length 일 때 EMPTY_ANNOTATED 패딩이 올바르게 적용되는지 확인한다.
    • 병합 후 mergedTrace[i]에 RawTraceStep + AnnotatedStep 필드가 모두 존재하는지 확인한다.
    • runtimeError와 aiError가 충돌 없이 공존하는지 확인한다.

  4. 결과 보고: 이슈가 있으면 파일명:라인 형태로 구체적으로 보고한다.

검증 체크리스트

  • Worker postMessage 페이로드 ⊇ RawTraceStep 필수 필드
  • varTypes 키 ⊇ rawTrace vars 키 합집합
  • var_mapping.var_name ∈ varTypes 키
  • mergedTrace.length === rawTrace.length (패딩 포함)
  • runtimeError step에서 aiError 공존 가능
  • EMPTY_ANNOTATED 패딩 시 explanation='', visual_actions=[], aiError=null
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. 27d ago First seen · 36 lines · 0 tokens per session scan A 066cfee7774c

Subscribe to this mod's changes

trace-validate is a command published in the GitHub repository ultra-ai-dle/frogger (8 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 565 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-10-02.

DebuggingTestingaialgorithm-visualizerdebuggerjavascript
Related

Other commands, from other repositories

implement-fix

Minimal pipeline for test-fixing tasks.

akaszubski/autonomous-dev · 11 tokens

playwright-test-heal

Run all my tests and fix the failing ones.

microsoft/playwright · 2 tokens

verify-bug

Post-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.

HoangNguyen0403/agent-skills-standard · 0 tokens

api-aqa-flow-execution-and-report-analysis

Phase 6 Execution & Report Analysis of api-aqa-flow (USER INTERACTION REQUIRED).

griddynamics/rosetta · 28 tokens

bugfix

Bug fix workflow: root cause analysis → user review → regression test + fix via TDD.

nWave-ai/nWave · 18 tokens

timeout-fix

A procedure for diagnosing and fixing tests that exceed their time limit by finding causes such as slow processing, hanging network calls, deadlocks, heavy setup, or leaked resources.

classmethod/tsumiki · 52 tokens