Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Kanevry/session-orchestratornpx agentmods add skills/kanevry/session-orchestrator/gitlab-opsWrote 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/kanevry/session-orchestrator/gitlab-ops)<a href="https://agentmods.dev/skills/kanevry/session-orchestrator/gitlab-ops"><img src="https://agentmods.dev/badge/skills/kanevry/session-orchestrator/gitlab-ops/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/kanevry/session-orchestrator/gitlab-ops"><img src="https://agentmods.dev/badge/skills/kanevry/session-orchestrator/gitlab-ops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, 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 Agent Snooping · line 9 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 13 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00174 | $0.00449 |
| Opus 5.5 | $0.00070 | $0.00180 |
| Sonnet 5.5 | $0.00035 | $0.00090 |
| Haiku 4.5 | $0.00017 | $0.00045 |
Grade A, and why
gitlab-ops 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 26d 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.
What it actually says
gitlab-ops
Portable mirror — generated, do not edit. The canonical workflow lives at
skills/gitlab-ops/SKILL.md; read that file for the full instructions. This mirror carries only agentskills.io-spec-legal frontmatter so harnesses that discover skills under.agents/skills/can find and route to the skill.Regenerate with
node scripts/generate-agents-skills.mjs.
Read the linked document in full and follow its complete workflow, including prechecks and stop conditions. Resolve its link relative to this SKILL.md, not the project working directory. The plugin root is three directories above this file. Resolve package paths such as skills/ and scripts/ from that root and relative links in the canonical document from its own directory. Keep the user’s project as the target of project operations.
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.
- 26d ago Changed · +2 lines fbf9cb303f5a
- 1mo ago Changed · +7 lines 2594d9ad58b4
- 1mo ago First seen · 14 lines · 174 tokens per session scan A 6ad34e6a9a4b
gitlab-ops is a skill published in the GitHub repository Kanevry/session-orchestrator (53 stars, last pushed 7d ago), licensed MIT. It adds 174 tokens to every session and 449 once invoked, about $0.0007 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
merge-review
Reviews pending fleet worktree merges before they're accepted. Reads the merge-check queue, detects file-level conflicts between branches, proposes a safe merge order, and surfaces reconciliation plans for overlapping changes.
next-issue
Work the next open item on the issue.
unleash
Run as a named worker draining the task queue in my private coordination repo, where each task is a GitHub Issue — claim one task at a time, check blocked-by dependencies, plan with explicit assumptions, execute, validate against acceptance criteria, and record results as comments; then stay in ambush behind a…
pace-release
A release-management workflow for coordinating software versions from preparation through deployment and closure. A release is a planned delivery of changes to users or an environment.
pace-sync
A skill that synchronizes development-planning records with GitHub Issues. GitHub Issues are task and discussion entries attached to a software project.
asana-sweep-setup
Set up asana-sweep in the current repository by deriving its GitLab and Asana configuration, confirming task-based scope rules, writing asana-sweep.config.json, and validating it with a dry run. Use when the user asks to set up, configure, or initialize asana-sweep.