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 aretw0/agents-lab --skill glabgit clone --depth 1 https://github.com/aretw0/agents-labWrote 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/aretw0/agents-lab/glab)<a href="https://agentmods.dev/skills/aretw0/agents-lab/glab"><img src="https://agentmods.dev/badge/skills/aretw0/agents-lab/glab/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/aretw0/agents-lab/glab"><img src="https://agentmods.dev/badge/skills/aretw0/agents-lab/glab.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.00030 | $0.00573 |
| Opus 5.5 | $0.00012 | $0.00229 |
| Sonnet 5.5 | $0.00006 | $0.00115 |
| Haiku 4.5 | $0.00003 | $0.00057 |
Grade A, and why
glab 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 1mo 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitLab Skill
Use the glab CLI to interact with GitLab. Always specify --repo namespace/project when not inside a git directory.
Provide all required fields explicitly to avoid interactive prompts:
glab mr create --title "..." --description "..." --yes
Issues
# List open issues
glab issue list --repo namespace/project
# View an issue
glab issue view 42 --repo namespace/project
# Create an issue
glab issue create --title "..." --description "..." --repo namespace/project
# Close an issue
glab issue close 42 --repo namespace/project
Merge Requests
# List MRs
glab mr list --repo namespace/project
# View an MR
glab mr view 55 --repo namespace/project
# Create an MR (always provide title and description)
glab mr create --title "..." --description "..." --yes --repo namespace/project
# Merge an MR
glab mr merge 55 --yes --repo namespace/project
# Check MR CI status
glab mr checks 55 --repo namespace/project
CI / Pipelines
# List recent pipelines
glab ci list --repo namespace/project
# View pipeline status
glab ci status --repo namespace/project
# View detailed pipeline jobs
glab ci view --repo namespace/project
# View logs for a specific job
glab ci trace --repo namespace/project
JSON Output
Use --output json for structured output and pipe to jq:
glab issue list --output json | jq '.[] | "\(.iid): \(.title)"'
glab mr list --output json | jq '.[] | "\(.iid) [\(.source_branch)]: \(.title)"'
# Get MR URL
glab mr view 55 --output json | jq .web_url
API for Advanced Queries
Use glab api for anything not covered by subcommands:
# Get project details
glab api projects/namespace%2Fproject
# List merge requests with specific fields
glab api projects/namespace%2Fproject/merge_requests --field state=opened \
| jq '.[] | "\(.iid): \(.title)"'
# Paginated results
glab api --paginate projects/namespace%2Fproject/issues | jq '.[].title'
Note: GitLab API uses URL-encoded namespace/project — replace / with %2F.
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.
- 1mo ago First seen · 96 lines · 30 tokens per session scan A d57867b220db
glab is a skill published in the GitHub repository aretw0/agents-lab (11 stars, last pushed 3mo ago), licensed MIT. It adds 30 tokens to every session and 573 once invoked, about $0.0001 per session on Opus 5.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
pi-review-gated-delivery
Use when coordinating review-gated delivery of discrete GitHub issues between one implementation peer and a review-only lead, with user-owned Changesets and approval-gated commits.
epic-close
Close out a completed EPIC / sprint end-to-end: author a fact-verified meta-post announcing what shipped, archive the EPIC's handovers, snapshot orchestrator memory, gate the integration→main merge on CI-green + explicit human go, drive the version bump (merge-commit conventions that auto-sync classifies), and verify…
speckit-taskstoissues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
create-issue
Draft and submit a GitHub issue from a user idea or bug description, with bilingual body and correct labels.
gh-assign-issues
Use to assign GitHub issues to a milestone and/or owners in bulk, verifying each.
meta-issue-to-pr-autopilot
Triages an issue, delegates the fix to sub-agent, drafts a PR description with summarize, and opens the PR via gh. Best used on small, well-scoped issues with clear acceptance criteria.