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.
npx agentmods add skills/greppable/greppable-cc-plugin/navigating-gdlc-code-mapsnpx skills add greppable/greppable-cc-plugin --skill navigating-gdlc-code-mapsgit clone --depth 1 https://github.com/greppable/greppable-cc-pluginWrote 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/skills/greppable/greppable-cc-plugin/navigating-gdlc-code-maps)<a href="https://agentmods.dev/skills/greppable/greppable-cc-plugin/navigating-gdlc-code-maps"><img src="https://agentmods.dev/badge/skills/greppable/greppable-cc-plugin/navigating-gdlc-code-maps.svg" alt="Measured on agentmods" 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 | $0.00130 | $0.01151 |
| Opus 5 | $0.00065 | $0.00575 |
| Sonnet 5 | $0.00026 | $0.00230 |
| Haiku 4.5 | $0.00013 | $0.00115 |
Grade A, and why
navigating-gdlc-code-maps 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GDLC Code Map Reference
Available Code Maps
!bash -c 'find docs/gdl -name "*.gdlc" -maxdepth 3 2>/dev/null | while read f; do count=$(grep -c "^@F" "$f" 2>/dev/null || echo 0); echo "- $f ($count files indexed)"; done'
Format
Two record types, one line each:
@D directory-path|description
@F file-path|lang|exports|imports|description
| Field | Content |
|---|---|
exports |
Comma-separated symbols exported by the file |
imports |
Comma-separated modules/packages imported |
lang |
Language identifier (ts, py, go, rs, etc.) |
description |
First sentence of the file's doc comment (may be empty) |
Files are grouped under their @D directory header. The file starts with # @VERSION and # @FORMAT comment headers.
Tool Functions
Source the helpers for exact-match lookups (prefer these over raw grep for symbol queries):
source "${CLAUDE_PLUGIN_ROOT}/scripts/gdlc-tools.sh"
| Function | Usage | What it does |
|---|---|---|
gdlc_files |
gdlc_files [DIR_PREFIX] [file.gdlc] |
List @F records, optionally filtered by directory prefix |
gdlc_exports |
gdlc_exports SYMBOL [file.gdlc] |
Find files exporting a symbol (exact match) |
gdlc_imports |
gdlc_imports MODULE [file.gdlc] |
Find files importing a module (exact match) |
gdlc_dirs |
gdlc_dirs [file.gdlc] |
List all @D directory records |
gdlc_lang |
gdlc_lang LANG [file.gdlc] |
List files by language (exact match, ts won't match tsx) |
Grep Patterns
Quick fuzzy searches (for exact matching, use the tool functions above):
# All files in a directory
grep "^@F apps/server/src/lib/" project.gdlc
# Fuzzy find a symbol (matches anywhere in the record)
grep "^@F.*symbolName" project.gdlc
# Find all files that import a module
grep "^@F.*|.*moduleName" project.gdlc
# All TypeScript files
grep "^@F.*|ts|" project.gdlc
# All directories
grep "^@D " project.gdlc
# Count files
grep -c "^@F " project.gdlc
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.
- 3d ago First seen · 113 lines · 130 tokens per session scan A d68f25f0bfaf
navigating-gdlc-code-maps is a skill published in the GitHub repository greppable/greppable-cc-plugin (3 stars, last pushed 4mo ago), licensed MIT. It adds 130 tokens to every session and 1,151 once invoked, about $0.0006 per session on Opus 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-08-31.
Other skills, from other repositories
ygrep
IMPORTANT: Try ygrep FIRST for all code and file searches before using Grep, Glob, or Task explore. ygrep uses a pre-built full-text index and returns results in milliseconds. Fall back to built-in tools only if ygrep returns no results.
semantic-search
Code search for this repo — pick the right Beacon tool for the question: exact symbol lookup, reference tracing, file outline, or semantic search.
ripgrep
Use when the user needs text or regex content search with ripgrep: composing rg commands, choosing flags, glob/type filtering, multiline or PCRE2 searches, pipeline output, grep-to-rg migration, or diagnosing why rg missed a file (gitignore, hidden, binary defaults). Not for syntax-aware structural queries (ast-grep)…
writing-docs
Write or restructure documentation that agents and people actually read — choosing which of the four directories it belongs in (how-to, reference, decisions, exec-plans), knowing what belongs in a failure message instead of a file, and keeping the routing table honest. Use this whenever writing a doc, a runbook, a…
repo-index
Give a repository a code-and-docs graph an agent can query — tree-sitter symbols, import and call edges, doc-to-code edges, ranked by personalized PageRank from whatever the current task touches. Use this when an agent cannot find the relevant code in a large repo, when grep returns hundreds of hits or none, when…
writing-checks
Build the machinery that enforces a convention instead of documenting it — PreToolUse guards that block an action before it runs, CI gates that judge the worktree, selftests that prove a check can turn red, and structural tests that enforce layering. Use this whenever a rule keeps getting violated despite being…