frogger: Command for Claude Code

.claude/commands/docs.md

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

A code-documentation command that updates architecture notes, comments, type descriptions, and diagrams to match the current code. It can scan all Markdown files for mismatches, but does not manage the README.

In plain words
What is it for?
Use it after a code change to update selected documentation areas or to audit the repository's Markdown and Mermaid diagrams.
Why use it?
Documentation can become misleading after code changes. This command checks claims against source files, settings, and types before changing them.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions CLAUDE.md.

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 →

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/docs.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 docs

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/ultra-ai-dle/frogger/docs"><img src="https://agentmods.dev/badge/commands/ultra-ai-dle/frogger/docs.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 2,161 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.02161
Opus 5.5 $0.00000 $0.00864
Sonnet 5.5 $0.00000 $0.00432
Haiku 4.5 $0.00000 $0.00216

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

Security

Grade A, and why

docs 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/docs.md · 108 lines

How it starts

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

/docs — 문서화 업데이트

목적

  • 변경된 코드를 기반으로 아키텍처 문서, 인라인 주석, 타입 JSDoc을 업데이트한다.
  • Markdown은 코드·실제 동작과 어긋나면 오해가 전파된다. align / audit 모드에서는 저장소의 Markdown 전체를 현재 코드베이스 기준으로 점검·수정한다. 본문뿐 아니라 Mermaid 등 다이어그램도 같은 기준으로 검증한다(그림 오해가 크므로 특히 엄하게). 기존 문서의 주장은 검증 전까지 신뢰하지 않고, 소스·설정·타입과 대조한다.

README는 수동 관리 대상이므로 이 커맨드의 범위가 아니다.

입력

  • $ARGUMENTS — (선택) arch, types, api, sync 등 영역. 미지정 시 브랜치 diff 기준 전체 스캔.
  • align 또는 audit — 아래 Markdown 전수 정합성 절차를 수행한다(mocks/ 제외, 문서만 수정, 보고서 제출).

실행 절차

A. 일반 모드 (align / audit 없음)

  1. 변경 감지: git diff main...HEAD로 변경 파일을 확인한다.

  2. 영역별 업데이트

    아키텍처 문서 (arch 또는 전체):

    • 문서 구조:
    • docs/architecture.md — 파이프라인 개요, 모듈 경계, 제약
    • docs/features/execution.md — Worker 실행
    • docs/features/trace.md — trace + 병합
    • docs/features/ai-pipeline.md — analyze 중심. POST /api/explain은 삭제 예정으로 취급해 제품 흐름·다이어그램에 넣지 않거나 삭제·축약한다.
    • docs/features/visualization.md — 시각화 전략
    • 포맷: 한줄 요약 → 데이터 흐름 → 모듈 경계 → 핵심 제약
    • 다이어그램은 Mermaid만 사용(ASCII 박스 금지). 차트 유형은 flowchart / sequenceDiagram / classDiagram 용도에 맞게 사용.
    • 다이어그램 검증:
      • 브라우저 ↔ Next ↔ 원격 JVM·LLM의 요청·응답 방향이 맞는지
      • Py·JS(Web Worker·postMessage)와 Java(fetch) 경로가 혼동 없이 드러나는지
      • 클라이언트가 LLM에 직접 붙는 잘못된 화살표가 없는지
      • 실제로는 언어 1개만 실행되는데 동시에 도는 것처럼 보이지 않는지
      • 수정 후 Mermaid 문법·미리보기로 화살표를 재검증
    • 변경된 파일이 아키텍처 경계(Worker 메시지, Store shape, API 계약)에 영향을 주면 해당 문서를 반영한다.
    • feature가 추가되면 docs/features/ 아래에 같은 포맷으로 새 문서를 생성한다.

    타입 JSDoc (types 또는 전체): src/types/prova.ts 누락·불일치 JSDoc 정리. AI·프롬프트가 참조하는 타입은 우선.

    API 라우트 (api 또는 전체):

    • /api/analyze, /api/java/execute의 request/response 스키마 주석 점검
    • 프롬프트 변경 시 입출력 계약이 주석과 일치하는지 확인
    • explain 라우트 파일이 있어도 문서에서는 삭제 예정·비노출로만 다루고, “현재 제품 기능”처럼 부풀리지 않는다.

    인라인 주석: 변경 파일에서 비자명한 부분만. 불일치 주석은 수정·삭제.

    기획서 싱크 (sync): prova.md vs 코드만 비교해 불일치 목록 출력, prova.md는 수정하지 않는다.

  3. 커밋: 변경된 내용을 바탕으로 아래 형식으로 커밋한다.

Read the full file on GitHub · 108 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. 27d ago First seen · 108 lines · 0 tokens per session scan A 565c33b39ce8

Subscribe to this mod's changes

docs 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 2,161 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.