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 skills add looker-open-source/looker-skills --skill lookml-modeling-guidelinesgit clone --depth 1 https://github.com/looker-open-source/looker-skillsWrote 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/looker-open-source/looker-skills/lookml-modeling-guidelines)<a href="https://agentmods.dev/skills/looker-open-source/looker-skills/lookml-modeling-guidelines"><img src="https://agentmods.dev/badge/skills/looker-open-source/looker-skills/lookml-modeling-guidelines/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/skills/looker-open-source/looker-skills/lookml-modeling-guidelines"><img src="https://agentmods.dev/badge/skills/looker-open-source/looker-skills/lookml-modeling-guidelines.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Memory Poisoning · line 46 Skill attempts to fill the context window with filler content, displacing legitimate instructions and safety constraints. This can degrade agent performance or bypass safety boundaries.Fix: Implement context-window management that detects and rejects padding or stuffing attempts. Prioritize system instructions over user-injected content.
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.00017 | $0.01947 |
| Opus 5 | $0.00009 | $0.00974 |
| Sonnet 5 | $0.00003 | $0.00389 |
| Haiku 4.5 | $0.00002 | $0.00195 |
Grade A, and why
lookml-modeling-guidelines 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 11d 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LookML Modeling Guidelines
This guide provides instructions on how to effectively use the Looker CLI to assist with LookML modeling tasks. It synthesizes best practices for LookML development with effective CLI usage.
LookML File Types
Understand the purpose of different file types in a LookML project:
- Project Manifest (
manifest.lkml): Global configuration for the project, including imports and constants. - Model Files (
.model.lkml): Defines database connections and Explores (how views are joined). - View Files (
.view.lkml): Blueprints for data, defining dimensions, measures, and derived tables. - Dashboard Files (
.dashboard.lookml): LookML-defined dashboards (layout, visualizations, filters). - Specialized Files: Refinement files (for overriding/patching), Data Test
files (automated logic checks), and Document files (
.md).
1. Analyzing Requirements
Before writing any LookML code or making modifications, analyze the user's request to determine the necessary LookML elements.
- Understand the Request: Identify the core business question or technical requirement.
- Identify Existing Resources:
- Use the Discovery tools (see section 2) to search the existing LookML project.
- Identify which existing columns (dimensions) and measures are best suited to answer the user prompt.
- Do not recreate existing logic. Reuse existing elements whenever possible.
- Determine Necessary Additions:
- Identify if any new LookML elements are required to fulfill the
prompt:
- New Views: Are we introducing new tables or derived tables?
(Note: If creating a derived table or PDT, you MUST consult the
lookml-pdt-guidelinesskill). - New Dimensions: Do we need to expose new columns or define new logic from existing columns?
- New Measures: Are we adding new aggregations (e.g.,
count,sum,average) or calculated metrics? - Other Elements: Do we need new joins in an Explore, or other LookML elements?
- New Views: Are we introducing new tables or derived tables?
(Note: If creating a derived table or PDT, you MUST consult the
- Identify if any new LookML elements are required to fulfill the
prompt:
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.
- 11d ago First seen · 186 lines · 17 tokens per session scan A 72a31d7e0d6c
lookml-modeling-guidelines is a skill published in the GitHub repository looker-open-source/looker-skills (28 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 1,947 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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
supabase
Supabase / PostgREST Row-Level-Security playbook — pull the anon (or leaked servicerole) key out of the frontend JS, map tables from the auto-generated OpenAPI spec, test anonymous RLS READ disclosures (PII/secret leaks), and anonymous RLS WRITE abuse (insert/update/delete — e.g. forging…
nornicdb-cypher-queries
Pick fast, predictable Cypher query shapes in NornicDB — point lookups, batch retrieval, pagination, search, traversal, batched UNWIND/MERGE writes, cleanup, multi-tenant isolation. Use when writing or reviewing Cypher whose latency or throughput matters; maps user intent to the executor's hot-path query templates.
dsql
Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, foreign key…