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 onboarding-preflight-checkgit 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/onboarding-preflight-check)<a href="https://agentmods.dev/skills/looker-open-source/looker-skills/onboarding-preflight-check"><img src="https://agentmods.dev/badge/skills/looker-open-source/looker-skills/onboarding-preflight-check/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/onboarding-preflight-check"><img src="https://agentmods.dev/badge/skills/looker-open-source/looker-skills/onboarding-preflight-check.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 Rogue Agent · line 5 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00043 | $0.00734 |
| Opus 5 | $0.00022 | $0.00367 |
| Sonnet 5 | $0.00009 | $0.00147 |
| Haiku 4.5 | $0.00004 | $0.00073 |
Grade A, and why
onboarding-preflight-check 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 12d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Looker Developer Onboarding: Pre-flight Check
This skill verifies that the local environment has the required tools and authentication configured before beginning onboarding.
Instructions
1. Run the System Pre-flight Check
Execute the pre-flight check script in system mode. Specify the path where you
plan to install the Looker CLI (typically ~/.local/bin or a workspace path):
./skills/onboarding-preflight-check/scripts/preflight_check.sh --mode system --install-dir ~/.local/bin
2. Handle Check Failures
If the script returns a non-zero exit code, resolve the issues based on the error output:
Case A: gcloud CLI is not installed
- Install the Google Cloud SDK. If you are unable to install it automatically (e.g. due to missing system package manager or permissions), instruct the user to install the Google Cloud SDK.
Case B: gcloud is not authenticated
-
Prompt the user to run the interactive login in their terminal:
gcloud auth login -
Wait for the user to complete the login flow, then re-run the check.
Case C: bq CLI is not installed
-
Install the
bqcomponent:gcloud components install bq
Case D: Installation directory ... is not writable
- Create the target installation directory if it does not exist. If
permissions are restricted, run the installation using a subdirectory in the
workspace (e.g.,
./bin) and pass that path to--install-dir.
3. Run the IAM Pre-flight Check (During Connection Setup)
Execute the pre-flight check script in iam mode to verify that the Looker Core
service account possesses the required least-privilege roles on the target GCP
project (roles/bigquery.dataViewer, roles/bigquery.jobUser, and
roles/serviceusage.serviceUsageConsumer):
./skills/onboarding-preflight-check/scripts/preflight_check.sh --mode iam --looker-project {looker_gcp_project_id} --bq-project {bigquery_gcp_project_id}
What ships with it
2 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.
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.
- 12d ago First seen · 88 lines · 43 tokens per session scan A 6f2bc8b6797e
onboarding-preflight-check 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 43 tokens to every session and 734 once invoked, about $0.0002 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
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…