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/exploring-gdla-api-contractsnpx skills add greppable/greppable-cc-plugin --skill exploring-gdla-api-contractsgit 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/exploring-gdla-api-contracts)<a href="https://agentmods.dev/skills/greppable/greppable-cc-plugin/exploring-gdla-api-contracts"><img src="https://agentmods.dev/badge/skills/greppable/greppable-cc-plugin/exploring-gdla-api-contracts.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.00117 | $0.01374 |
| Opus 5 | $0.00059 | $0.00687 |
| Sonnet 5 | $0.00023 | $0.00275 |
| Haiku 4.5 | $0.00012 | $0.00137 |
Grade A, and why
exploring-gdla-api-contracts 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 4d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GDLA Quick Reference
Available API Contracts
!bash -c 'find docs/gdl -name "*.gdla" -maxdepth 3 2>/dev/null | while read f; do echo "- $f"; done'
Format
@D service-name|description|version|base-url
@S SchemaName|description
field|type|required|format|description
@EP METHOD /path|description|responses|auth
@P param|location|type|required|description
@AUTH scheme|description|header
@ENUM Name|value1,value2,value3
@R Source -> Target|relationship|via field
@PATH Entity -> Entity|traversal description
Endpoints and auth are single-line records. Schemas use indented field lines (like GDLS tables).
Grep Patterns
# All endpoints
grep "^@EP" contract.gdla
# Specific HTTP method
grep "^@EP GET" contract.gdla
grep "^@EP POST" contract.gdla
# GraphQL operations
grep "^@EP QUERY" contract.gdla
grep "^@EP MUTATION" contract.gdla
grep "^@EP SUBSCRIPTION" contract.gdla
# Find a schema and its fields
grep "@S Pet" -A 20 contract.gdla
# All schemas (just headers)
grep "^@S " contract.gdla
# Parameters for an endpoint
grep "^@EP GET /pets" -A 10 contract.gdla | grep "^@P"
# Authentication schemes
grep "^@AUTH" contract.gdla
# Endpoints requiring specific auth
grep "^@EP.*|bearer" contract.gdla
# Schema relationships
grep "^@R" contract.gdla
# Traversal paths
grep "^@PATH" contract.gdla
# Enums
grep "^@ENUM" contract.gdla
# Cross-file: all endpoints across all APIs
grep "^@EP" *.gdla
# Cross-file: find which APIs use bearer auth
grep "^@AUTH.*bearer" *.gdla
Combined Queries (Fewer Tool Calls)
# Full API surface (endpoints + auth)
grep -E "^@EP|^@AUTH" contract.gdla
# Schema + relationships
grep -E "^@S |^@R " contract.gdla
# All constraints (enums + required fields)
grep -E "^@ENUM|required" contract.gdla
# Endpoints that return a specific schema
grep "^@EP.*Pet" contract.gdla
# Cross-API: all endpoints and their auth across all contracts
grep -E "^@EP|^@AUTH" *.gdla
Tool Functions
Source the helpers:
source "${CLAUDE_PLUGIN_ROOT}/scripts/gdla-tools.sh"
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.
- 4d ago First seen · 150 lines · 117 tokens per session scan A ecec09c98600
exploring-gdla-api-contracts is a skill published in the GitHub repository greppable/greppable-cc-plugin (3 stars, last pushed 4mo ago), licensed MIT. It adds 117 tokens to every session and 1,374 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…