Borrowing it
Nothing to install: this file belongs to akiojin/llmlb. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/akiojin/llmlb/develop/.claude/commands/gwt-project-index.mdgit clone --depth 1 https://github.com/akiojin/llmlbWrote 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.
[](https://agentmods.dev/commands/akiojin/llmlb/gwt-project-index)<a href="https://agentmods.dev/commands/akiojin/llmlb/gwt-project-index"><img src="https://agentmods.dev/badge/commands/akiojin/llmlb/gwt-project-index/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.
<a href="https://agentmods.dev/commands/akiojin/llmlb/gwt-project-index"><img src="https://agentmods.dev/badge/commands/akiojin/llmlb/gwt-project-index.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00013 | $0.00217 |
| Opus 5.5 | $0.00005 | $0.00087 |
| Sonnet 5.5 | $0.00003 | $0.00043 |
| Haiku 4.5 | $0.00001 | $0.00022 |
Grade A, and why
gwt-project-index 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.
What it actually says
GWT Project Index Command
Use this command to run semantic search against the project structure index.
Usage
/gwt:gwt-project-index [query]
Steps
- Load
.claude/skills/gwt-project-index/SKILL.mdand follow the workflow. - If index status is unknown, check index health before searching.
- Run semantic search and return top results with short rationale:
- path
- relevance summary
- next file(s) to inspect
- If index is missing/outdated, explain that and provide the shortest recovery action.
- For Issue search, use
/gwt:gwt-issue-searchinstead.
Examples
/gwt:gwt-project-index where branch naming is built
/gwt:gwt-project-index project mode pty orchestration
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 · 37 lines · 13 tokens per session scan A ce057faf3d5e
gwt-project-index is a command published in the GitHub repository akiojin/llmlb (10 stars, last pushed 3d ago), licensed MIT. It adds 13 tokens to every session and 217 once invoked, about $0.0001 per session on Opus 5.5. 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-21.
Other commands, from other repositories
rag-audit
Report quality and best-practice gaps in an existing implementation. TRIGGER WHEN: the user asks to review, audit, or validate a RAG pipeline: chunking, embeddings, retrieval, reranking, or production readiness. DO NOT TRIGGER WHEN: building from scratch (use rag-architect), or auditing a pure vector database (use…
rag-debug
Walk the 9-layer RAG failure diagnostic chain against a specific failing query.
rag-failure-trace
Capture a full RAG audit trace for a query — useful for debugging or seeding a regression test.
review-code
Review code for quality, security, and maintainability. Dispatches all relevant reviewer agents in parallel and merges findings by severity.
rag-debug
Debug RAG pipeline issues with systematic retrieval and generation analysis.
querying
Query documents from a search index using type-safe filters with support for pagination, sorting, field selection, scoring, and highlighting. Count matching documents efficiently without returning results.