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/yunseo-kim/agent-toolbox/gitlab-ci-patternsnpx skills add yunseo-kim/agent-toolbox --skill gitlab-ci-patternsgit clone --depth 1 https://github.com/yunseo-kim/agent-toolboxWrote 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/yunseo-kim/agent-toolbox/gitlab-ci-patterns)<a href="https://agentmods.dev/skills/yunseo-kim/agent-toolbox/gitlab-ci-patterns"><img src="https://agentmods.dev/badge/skills/yunseo-kim/agent-toolbox/gitlab-ci-patterns.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.00046 | $0.01494 |
| Opus 5 | $0.00023 | $0.00747 |
| Sonnet 5 | $0.00009 | $0.00299 |
| Haiku 4.5 | $0.00005 | $0.00149 |
Grade A, and why
gitlab-ci-patterns 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 6d ago First seen · 272 lines · 46 tokens per session scan A 109b4492fc27
gitlab-ci-patterns is a skill published in the GitHub repository yunseo-kim/agent-toolbox (1 stars, last pushed yesterday), with no licence file. It adds 46 tokens to every session and 1,494 once invoked, about $0.0002 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
bash-defensive-patterns
Master defensive Bash programming techniques for production-grade scripts. Use when writing robust shell scripts, CI/CD pipelines, or system utilities requiring fault tolerance and safety.
bats-testing-patterns
Master Bash Automated Testing System (Bats) for comprehensive shell script testing. Use when writing tests for shell scripts, CI/CD pipelines, or requiring test-driven development of shell utilities.
bash-pro
Master of defensive Bash scripting for production automation, CI/CD.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
ci-all
Full CI pipeline: run local tests, type check, push branch, and return the pipeline URL. The only command you need before opening a PR.
ci-pipeline
Push current branch and return the pipeline tracking URL (GitLab or GitHub Actions).