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 frontier-ai-next/mgarlbot --skill gitlab_pages_cigit clone --depth 1 https://github.com/frontier-ai-next/mgarlbotWrote 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/frontier-ai-next/mgarlbot/gitlab_pages_ci)<a href="https://agentmods.dev/skills/frontier-ai-next/mgarlbot/gitlab_pages_ci"><img src="https://agentmods.dev/badge/skills/frontier-ai-next/mgarlbot/gitlab_pages_ci/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/frontier-ai-next/mgarlbot/gitlab_pages_ci"><img src="https://agentmods.dev/badge/skills/frontier-ai-next/mgarlbot/gitlab_pages_ci.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.00711 |
| Opus 5 | $0.00015 | $0.00356 |
| Sonnet 5 | $0.00006 | $0.00142 |
| Haiku 4.5 | $0.00003 | $0.00071 |
Grade A, and why
gitlab_pages_ci 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 10d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitLab CI + Pages
The GitLab Runner executes the pipeline, not the bot. Your job is to add or fix .gitlab-ci.yml in the repo and list what to enable in GitLab (Settings → Pages, visibility).
General layout
stages: [test, deploy](or[test, pages]).- test job: same stack as local (Python/Node/Go). Default image from process env
GITLAB_CI_DEFAULT_IMAGE(e.g.python:3.12-bookworm) — use it in YAML if the project has noimage:. - pages job: GitLab requires a
public/artifact. Build the static site (MkDocs, VitePress,sphinx -b html, SPAnpm run buildthen copy intopublic/) and declare:
pages:
stage: deploy
needs: ["test"]
script:
- mkdir -p public
- cp -r dist/* public/ # example; adapt to the project
artifacts:
paths:
- public
Python (pytest) + minimal Pages stub
Template “tests + placeholder site”:
stages: [test, deploy]
variables:
PIP_CACHE_DIR: "$CI_PROJECT_DIR/.cache/pip"
test:
stage: test
image: python:3.12-bookworm
cache:
paths: [.cache/pip]
before_script:
- python -m pip install -U pip
- test -f requirements.txt && pip install -r requirements.txt || true
- test -f pyproject.toml && pip install -e ".[dev]" || true
script:
- pytest -q || true
pages:
stage: deploy
needs: ["test"]
image: alpine:latest
script:
- mkdir -p public
- echo '<!doctype html><meta charset=utf-8><title>CI</title><p>GitLab Pages OK</p>' > public/index.html
artifacts:
paths: [public]
Tune pytest for the real layout (tests/, uv run, etc.).
Node / static frontend
image: node:22-bookworm(or project LTS).cache: { paths: [node_modules/] }script: npm ci && npm run build→ output indist/orbuild/→ copy intopublic/.
Important
- No secrets in YAML; use GitLab CI/CD Variables (masked).
- If
.gitlab-ci.ymlalready exists — extend stages/jobs; do not break production-branch deploy without explicit user approval. - After merge: Pages URL like
https://<namespace>.gitlab.io/<project>/(depends on settings); tell the user to check Deploy → Pages in the UI.
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.
- 10d ago First seen · 77 lines · 30 tokens per session scan A 7521b48463e7
gitlab_pages_ci is a skill published in the GitHub repository frontier-ai-next/mgarlbot (17 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 711 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-30.
Other skills, from other repositories
test-environment-management
Test environment provisioning, infrastructure as code for testing, Docker/Kubernetes for test environments, service virtualization, and cost optimization. Use when managing test infrastructure, ensuring environment parity, or optimizing testing costs.
devops-infra
DevOps & Infrastructure (Docker, AWS, Messaging): Helps with Docker configuration, AWS architecture, CI/CD pipelines, Kubernetes, monitoring, and messaging infrastructure (Kafka, SQS, SNS). Use whenever the user wants to review or create Dockerfiles, docker-compose configs, AWS architecture, CI/CD pipelines…
DevOps & Deployment
CI/CD pipelines, containerization, Kubernetes, and infrastructure as code patterns.
architecture-diagram
Dark-themed SVG architecture/cloud/infra diagrams as HTML.
scanning-docker-images-with-trivy
Trivy is a comprehensive open-source vulnerability scanner by Aqua Security that detects vulnerabilities in OS packages, language-specific dependencies, misconfigurations, secrets, and license violati.
start-temps-cluster
Start (or restart) a local multi-node Temps cluster using Docker-in-Docker — one control plane + 3 worker nodes, each a privileged DinD container running its own dockerd + temps agent, wired with the real multi-host overlay (VXLAN, computecidr allocation) via tools/dev-cluster/ in whichever checkout/worktree you run…