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 bdiasti/maestro-bundle-cli --skill ci-cd-pipelinegit clone --depth 1 https://github.com/bdiasti/maestro-bundle-cliWrote 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/bdiasti/maestro-bundle-cli/ci-cd-pipeline)<a href="https://agentmods.dev/skills/bdiasti/maestro-bundle-cli/ci-cd-pipeline"><img src="https://agentmods.dev/badge/skills/bdiasti/maestro-bundle-cli/ci-cd-pipeline.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.00052 | $0.01433 |
| Opus 5 | $0.00026 | $0.00717 |
| Sonnet 5 | $0.00010 | $0.00287 |
| Haiku 4.5 | $0.00005 | $0.00143 |
Grade A, and why
ci-cd-pipeline scanned grade A with 1 finding 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 7d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl --header "PRIVATE-TOKEN: $TOKEN" \ How it starts
The opening of the file, as written. The whole thing — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI/CD Pipeline
Create and configure GitLab CI pipelines for JHipster microservices with stages for lint, test, security, compliance, build, and deploy.
When to Use
- When setting up CI/CD for a new microservice
- When adding quality gates (lint, test, security scan)
- When automating Docker builds and pushes
- When configuring deployment to K3s/Kubernetes
- When adding compliance checks
Available Operations
- Create
.gitlab-ci.ymlwith all stages - Configure lint and test stages
- Set up Docker image build with Jib
- Configure deployment to Kubernetes
- Add security scanning
Multi-Step Workflow
Step 1: Create Pipeline File
# .gitlab-ci.yml
stages:
- lint
- test
- security
- build
- deploy-staging
- deploy-prod
variables:
DOCKER_IMAGE: $CI_REGISTRY_IMAGE
K3S_NAMESPACE: maestro
MAVEN_OPTS: "-Dmaven.repo.local=$CI_PROJECT_DIR/.m2/repository"
cache:
paths:
- .m2/repository/
- node_modules/
Step 2: Add Lint and Test Stages
lint:backend:
stage: lint
image: maven:3.9-eclipse-temurin-21
script:
- ./mvnw checkstyle:check -DskipTests
- ./mvnw pmd:check -DskipTests
lint:frontend:
stage: lint
image: node:20-slim
script:
- npm ci
- npm run lint
test:backend:
stage: test
image: maven:3.9-eclipse-temurin-21
services:
- postgres:16
variables:
SPRING_DATASOURCE_URL: jdbc:postgresql://postgres:5432/testdb
SPRING_DATASOURCE_USERNAME: test
SPRING_DATASOURCE_PASSWORD: test
script:
- ./mvnw verify -Pprod -DskipTests=false
- ./mvnw test -Dtest="*IT" -DfailIfNoTests=false
artifacts:
reports:
junit: target/surefire-reports/*.xml
test:frontend:
stage: test
image: node:20-slim
script:
- npm ci
- npm test -- --coverage
Step 3: Add Security Scanning
security:dependencies:
stage: security
image: maven:3.9-eclipse-temurin-21
script:
- ./mvnw org.owasp:dependency-check-maven:check
allow_failure: true
artifacts:
paths:
- target/dependency-check-report.html
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.
- 7d ago First seen · 203 lines · 52 tokens per session scan A 23b7b85d1b4f
ci-cd-pipeline is a skill published in the GitHub repository bdiasti/maestro-bundle-cli (21 stars, last pushed 5mo ago), licensed MIT. It adds 52 tokens to every session and 1,433 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.