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/vince-winkintel/gitlab-cli-skills/glab-orbitnpx skills add vince-winkintel/gitlab-cli-skills --skill glab-orbitgit clone --depth 1 https://github.com/vince-winkintel/gitlab-cli-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/vince-winkintel/gitlab-cli-skills/glab-orbit)<a href="https://agentmods.dev/skills/vince-winkintel/gitlab-cli-skills/glab-orbit"><img src="https://agentmods.dev/badge/skills/vince-winkintel/gitlab-cli-skills/glab-orbit.svg" alt="Measured on agentmods" 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.00074 | $0.01730 |
| Opus 5 | $0.00037 | $0.00865 |
| Sonnet 5 | $0.00015 | $0.00346 |
| Haiku 4.5 | $0.00007 | $0.00173 |
Grade A, and why
glab-orbit 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 6d 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
glab orbit
Run the managed Orbit CLI for the GitLab Knowledge Graph (product name: Orbit) through glab.
glab orbit routes through the managed orbit-cli binary. glab downloads, verifies, and updates that binary on first use, then forwards commands and flags verbatim. glab orbit remote <command> injects the resolved GitLab credential; other Orbit commands run the managed binary without extra auth environment.
⚠️ Experimental Feature
Upstream marks Orbit as EXPERIMENTAL:
- most command shape now belongs to the managed
orbit-clibinary and may change independently - the API is gated behind the
knowledge_graphfeature flag - access is user-scoped, not project-scoped
glab orbit --installandglab orbit --updateinstall or refresh the managed binary without running it
See: https://docs.gitlab.com/policy/development_stages_support/
Quick start
# First: confirm the service is available for your user; glab injects auth for remote commands
glab orbit remote status
# Guided onboarding through the Orbit binary
glab orbit setup claude
# Discover the graph model through orbit-cli
glab orbit remote schema
glab orbit remote dsl
glab orbit remote tools
# Install or update the managed binary without running a command
glab orbit --install
glab orbit --update
Recommended workflow: discover first, query second
Use the Orbit binary's discovery-first flow:
glab orbit setup claudeorglab orbit remote status— verify Orbit is enabled and reachableglab orbit remote schema— inspect the ontology (entities, edges, properties)glab orbit remote dsl— inspect the authoritative JSON Schema for the query DSLglab orbit remote tools— inspect the MCP tool manifest when integrating with agents/toolsglab orbit remote query ...— run actual graph queries once you know the schema
That order matters because schema and dsl are the source of truth for what the graph exposes and what request bodies are valid; tools is still useful for MCP/agent integration metadata.
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.
- 6d ago First seen · 208 lines · 74 tokens per session scan A e0dfb27033f9
glab-orbit is a skill published in the GitHub repository vince-winkintel/gitlab-cli-skills (47 stars, last pushed 4d ago), licensed MIT. It adds 74 tokens to every session and 1,730 once invoked, about $0.0004 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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
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…