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 authenticating-looker-cligit 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/authenticating-looker-cli)<a href="https://agentmods.dev/skills/looker-open-source/looker-skills/authenticating-looker-cli"><img src="https://agentmods.dev/badge/skills/looker-open-source/looker-skills/authenticating-looker-cli/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/authenticating-looker-cli"><img src="https://agentmods.dev/badge/skills/looker-open-source/looker-skills/authenticating-looker-cli.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 28 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.00045 | $0.00856 |
| Opus 5 | $0.00023 | $0.00428 |
| Sonnet 5 | $0.00009 | $0.00171 |
| Haiku 4.5 | $0.00005 | $0.00086 |
Grade A, and why
authenticating-looker-cli 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 10d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Authenticating Looker CLI
Authenticates the Looker CLI to a Looker instance using OAuth and saves the session configuration in a named profile.
Prerequisites
- Looker CLI must be installed (see
installing-looker-cliskill). - You must know the Looker instance URL (host and API port). Generically, the
API port is
443for Looker Core / Google Cloud Core.
Instructions
1. Configure a Named Profile
Create a new profile named default to save your connection details:
looker-cli profile add default --host {instance_host} --port {instance_port}
Set this new profile as your default configuration:
looker-cli profile use default
2. Trigger OAuth Login
Run the login command in the background (since it requires interactive browser authorization):
looker-cli session login --oauth
3. Retrieve the Authorization URL
Monitor the background login task log or stdout to extract the generated login URL. Looker CLI will output:
Opening browser to URL: followed by a long URL.
4. Instruct the User (Interactive Step)
Present the login URL to the user and instruct them:
"Please open the following URL in your browser, log in to Looker, and authorize the CLI:
URL: {auth_url}
If you are running on a local desktop machine, the login should complete automatically once authorized. If you are on a remote server/headless workspace, the browser will show a page load error or try to redirect to
http://127.0.0.1:7777/?code=.... Please copy the entire redirected URL from your browser's address bar and paste it back into the terminal prompt."
5. Handle the OAuth Response
- Scenario A (Automatic): If the user completes authentication and the CLI is listening locally on port 7777, the login command task will finish successfully.
- Scenario B (Headless Fallback): The background process will print:
Paste redirected URL here:If the user pastes the redirected URL, usemanage_taskwithsend_inputto pass the pasted URL directly to the background login task.
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.
- 10d ago First seen · 111 lines · 45 tokens per session scan A 3d431e9b162c
authenticating-looker-cli 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 45 tokens to every session and 856 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…