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/gemini-cli-extensions/looker/looker-devnpx skills add gemini-cli-extensions/looker --skill looker-devgit clone --depth 1 https://github.com/gemini-cli-extensions/lookerWhat 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.00026 | $0.05254 |
| Opus 5 | $0.00013 | $0.02627 |
| Sonnet 5 | $0.00005 | $0.01051 |
| Haiku 4.5 | $0.00003 | $0.00525 |
Grade A, and why
looker-dev 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 — 682 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Usage
All scripts can be executed using Node.js. Replace <param_name> and <param_value> with actual values.
Bash:
node <skill_dir>/scripts/<script_name>.js '{"<param_name>": "<param_value>"}'
PowerShell:
node <skill_dir>/scripts/<script_name>.js '{\"<param_name>\": \"<param_value>\"}'
Note: The scripts automatically load the environment variables from various .env files. Do not ask the user to set vars unless skill executions fails due to env var absence.
Scripts
create_git_branch
This skill is used to create a new git branch of a LookML project. This only works in dev mode.
Parameters:
- project_id (required): The unique ID of the LookML project.
- branch (required): The branch to create.
- ref (optional): The ref to start a newly created branch.
Parameters
| Name | Type | Description | Required | Default |
|---|---|---|---|---|
| project_id | string | The project_id | Yes | |
| branch | string | The git branch to create | Yes | |
| ref | string | The ref to use as the start of a new branch. Defaults to HEAD of current branch if not specified. | No | `` |
create_project_directory
This skill creates a new directory within a specified LookML project.
Prerequisite: The Looker session must be in Development Mode. Use dev_mode: true first.
Parameters:
- project_id (required): The unique ID of the LookML project.
- directory_path (required): The path to the new directory within the project.
Output: A confirmation message upon successful directory creation.
Parameters
| Name | Type | Description | Required | Default |
|---|---|---|---|---|
| project_id | string | The id of the project | Yes | |
| directory_path | string | The path to create in the project | Yes |
create_project_file
This skill creates a new LookML file within a specified project, populating it with the provided content.
Prerequisite: The Looker session must be in Development Mode. Use dev_mode: true first.
What ships with it
27 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- scripts/create_git_branch.js 3.2 KB runs code
- scripts/create_project_directory.js 3.2 KB runs code
- scripts/create_project_file.js 3.2 KB runs code
- scripts/create_view_from_table.js 3.2 KB runs code
- scripts/delete_git_branch.js 3.2 KB runs code
- scripts/delete_project_directory.js 3.2 KB runs code
- scripts/delete_project_file.js 3.2 KB runs code
- scripts/dev_mode.js 3.2 KB runs code
- scripts/get_connection_databases.js 3.2 KB runs code
- scripts/get_connection_schemas.js 3.2 KB runs code
- scripts/get_connection_table_columns.js 3.2 KB runs code
- scripts/get_connection_tables.js 3.2 KB runs code
- scripts/get_connections.js 3.2 KB runs code
- scripts/get_git_branch.js 3.2 KB runs code
- scripts/get_lookml_tests.js 3.2 KB runs code
- scripts/get_project_directories.js 3.2 KB runs code
- scripts/get_project_file.js 3.2 KB runs code
- scripts/get_project_files.js 3.2 KB runs code
- scripts/get_projects.js 3.2 KB runs code
- scripts/health_analyze.js 3.2 KB runs code
- scripts/health_pulse.js 3.2 KB runs code
- scripts/health_vacuum.js 3.2 KB runs code
- scripts/list_git_branches.js 3.2 KB runs code
- scripts/run_lookml_tests.js 3.2 KB runs code
- scripts/switch_git_branch.js 3.2 KB runs code
- scripts/update_project_file.js 3.2 KB runs code
- scripts/validate_project.js 3.2 KB runs code
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 · 682 lines · 26 tokens per session scan A 5bb69c68c829
looker-dev is a skill published in the GitHub repository gemini-cli-extensions/looker (54 stars, last pushed 6d ago), licensed Apache-2.0. It adds 26 tokens to every session and 5,254 once invoked, about $0.0001 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-30.
Other skills, from other repositories
cloud-sql-postgres-health
Use these skills when you need to audit database health, identify storage bloat, find invalid indexes, analyze table statistics, and manage maintenance configurations like autovacuum.
cloud-sql-postgres-vectorassist
Use these skills to set up and optimize production-ready vector workloads by simply expressing your intent and performance requirements.
cloud-sql-postgres-data
Use these skills when you need to explore the database structure, discover schema objects like views or stored procedures, and execute custom SQL queries to interact with your data.
cloud-sql-postgres-admin
Use these skills when you need to provision new Cloud SQL instances, create databases and users, clone existing environments, and monitor the progress of long-running operations.
cloud-sql-postgres-lifecycle
Use these skills when you need to manage the lifecycle of your instances, including performing backups and restores, checking major version upgrade compatibility, and monitoring overall instance status.
cloud-sql-postgres-replication
Use these skills when you need to monitor replication health, manage sync states between nodes, and audit database roles and security settings to ensure environment integrity.