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 speedscale/speedy-template --skill glab-speedscalegit clone --depth 1 https://github.com/speedscale/speedy-templateWrote 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/speedscale/speedy-template/glab-speedscale)<a href="https://agentmods.dev/skills/speedscale/speedy-template/glab-speedscale"><img src="https://agentmods.dev/badge/skills/speedscale/speedy-template/glab-speedscale/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/speedscale/speedy-template/glab-speedscale"><img src="https://agentmods.dev/badge/skills/speedscale/speedy-template/glab-speedscale.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.00056 | $0.00974 |
| Opus 5.5 | $0.00022 | $0.00390 |
| Sonnet 5.5 | $0.00011 | $0.00195 |
| Haiku 4.5 | $0.00006 | $0.00097 |
Grade A, and why
glab-speedscale 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 2mo 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitLab Merge Requests
Manage GitLab merge requests using the glab CLI.
All glab commands must include --repo your-org/your-repo to target the correct repository.
Core Commands
List MRs
glab mr list --repo your-org/your-repo
glab mr list --repo your-org/your-repo --all # include closed/merged
glab mr list --repo your-org/your-repo --author @me # your MRs
View MR Details
glab mr view <mr-number> --repo your-org/your-repo
glab mr view <mr-number> --repo your-org/your-repo --comments # with comments
glab mr diff <mr-number> --repo your-org/your-repo # full diff
Create an MR
Before creating, read references/mr-guidelines.md for title format, description structure, and mandatory checklist.
glab mr create \
--repo your-org/your-repo \
--title "[SPD-xxx] component: description" \
--description "$(cat mr_description.md)" \
--source-branch <source-branch> \
--target-branch master \
--assignee @me
Enable Auto-Merge
glab mr merge <mr-number> --repo your-org/your-repo --auto-merge --remove-source-branch
Auto-merge triggers once all approvals are received, CI passes, and discussions are resolved.
Comment on an MR
IMPORTANT: All comments MUST start with === bot === on its own line. The agent uses your personal credentials — this prefix distinguishes bot actions from human actions for auditability.
glab mr note <mr-number> --repo your-org/your-repo --message "=== bot ===
Your comment here"
Check Pipeline Status
glab mr view <mr-number> --repo your-org/your-repo # pipeline status in MR details
glab ci view --repo your-org/your-repo --branch <branch> # detailed CI info
Close an MR
glab mr close <mr-number> --repo your-org/your-repo
If someone closes YOUR MR: STOP. Do not recreate it. See references/mr-guidelines.md — the closure is intentional.
MR Tracking
After creating an MR, add it to the tracked_mrs array in memory/speedy-mrs.json for heartbeat monitoring:
What ships with it
1 file 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.
- 2mo ago First seen · 122 lines · 56 tokens per session scan A 081414b97f05
glab-speedscale is a skill published in the GitHub repository speedscale/speedy-template (5 stars, last pushed 8mo ago), licensed MIT. It adds 56 tokens to every session and 974 once invoked, about $0.0002 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-31.
Other skills, from other repositories
pr
Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…