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 glassity/agent-skills --skill glassity-authgit clone --depth 1 https://github.com/glassity/agent-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/glassity/agent-skills/glassity-auth)<a href="https://agentmods.dev/skills/glassity/agent-skills/glassity-auth"><img src="https://agentmods.dev/badge/skills/glassity/agent-skills/glassity-auth/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/glassity/agent-skills/glassity-auth"><img src="https://agentmods.dev/badge/skills/glassity/agent-skills/glassity-auth.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00097 | $0.00783 |
| Opus 5 | $0.00048 | $0.00392 |
| Sonnet 5 | $0.00019 | $0.00157 |
| Haiku 4.5 | $0.00010 | $0.00078 |
Grade A, and why
glassity-auth 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Glassity authentication
When to use
- The user says "log in to Glassity", "connect Glassity", "auth with Glassity"
- The user asks "who am I on Glassity", "which tenant am I using", "show my scopes"
- The user wants to clear credentials ("log out of Glassity")
- Any Glassity skill reports
not authenticated(exit code 3)
Binary check
Run command -v glassity before the first CLI call. If it is missing, stop and
tell the user to install it with brew install glassity/tap/glassity or from
https://github.com/glassity/cli/releases. No account yet? Sign up at
app.glassity.cloud.
Signing in
glassity auth login
This prints a URL and a short code. The user opens the URL in a browser on any device, signs in, and the credential is written to the OS keychain. Nothing has to launch a browser on this machine, so it works over SSH, in dev containers, and under WSL.
Show the user the printed URL and code verbatim, then wait — the command completes once they finish in the browser.
Checking the active tenant
glassity --output=json auth whoami
Returns the tenant name, account_prefix_id, AWS account ids, scopes, and
token expiry. Always repeat the tenant and AWS account back to the user so a
wrong-tenant session is caught before anything is read or written.
Headless and CI
A CI runner has no browser and often no keychain. Mint a Personal Access Token in the Glassity web app and pass it through the environment:
export GLASSITY_TOKEN=<pat>
glassity --output=json opp list
GLASSITY_TOKEN takes precedence over the keychain, so nothing is written to
disk on the runner.
Where a keychain does exist and the user wants a token stored persistently instead of an OAuth session, pipe the secret so it never reaches argv:
echo "$GLASSITY_PAT" | glassity auth set-token --token=-
The binary validates the token against the API before persisting it, then
writes the resolved tenant defaults into the profile so later commands do not
need --account.
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 · 87 lines · 97 tokens per session scan A 5232f6d1e3db
glassity-auth is a skill published in the GitHub repository glassity/agent-skills (2 stars, last pushed 29d ago), licensed Apache-2.0. It adds 97 tokens to every session and 783 once invoked, about $0.0005 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
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…