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 thermiteau/maverick --skill mav-bp-cicdgit clone --depth 1 https://github.com/thermiteau/maverickWrote 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/thermiteau/maverick/mav-bp-cicd)<a href="https://agentmods.dev/skills/thermiteau/maverick/mav-bp-cicd"><img src="https://agentmods.dev/badge/skills/thermiteau/maverick/mav-bp-cicd/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/thermiteau/maverick/mav-bp-cicd"><img src="https://agentmods.dev/badge/skills/thermiteau/maverick/mav-bp-cicd.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.00045 | $0.00831 |
| Opus 5 | $0.00023 | $0.00415 |
| Sonnet 5 | $0.00009 | $0.00166 |
| Haiku 4.5 | $0.00005 | $0.00083 |
Grade A, and why
mav-bp-cicd 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 12d 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.
| Bitbucket Pipelines | `curl .../2.0/repositories/<ws>/<repo>/pipelines/?sort=-created_on` | pipeline page / API step logs | How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI/CD Standards
Pipeline standards and the post-push monitoring loop. CI is the last line of defence for autonomous work: it does not hallucinate, skip steps, or declare success prematurely.
Maverick's Rules
- Every stage gates the next; cheapest checks first (lint/typecheck),
expensive last. Never skip stages — no
[skip ci], no conditional bypasses for "quick fixes". - Build once, promote the same artifact — never rebuild for production; only environment config changes between environments.
- Secrets come from the platform's secret store, never the repository. Pin action/image versions.
- Production deploys are human-gated. Hotfixes follow the same pipeline, just expedited.
- Failing gates are fixed, never bypassed — no
--no-verify, no force merge, no editing gate config to get green (gate configuration is infrastructure; see Boundaries).
Monitoring CI After Push
After every push, monitor the pipeline with the platform CLI, read the
failed job's logs, fix locally, and re-push. From a do-issue-*
workflow, use the bounded wait: uv run maverick pr wait <repo> <pr-num> --checks --timeout 30m.
| Platform | Status | Logs |
|---|---|---|
| GitHub Actions | gh run list --branch <br> / gh pr checks <pr> |
gh run view <id> --log-failed |
| GitLab CI | glab ci status |
glab ci trace <job> |
| Azure DevOps | az pipelines runs list --branch <br> |
az pipelines runs show --id <id> |
| Bitbucket Pipelines | curl .../2.0/repositories/<ws>/<repo>/pipelines/?sort=-created_on |
pipeline page / API step logs |
Anything genuinely project-specific (required checks, runner quirks, deploy targets) belongs in the project skill, not here.
Project Implementation Lookup
Check docs/maverick/skills/cicd/SKILL.md for the project's pipeline
platform, stages, required checks, and deployment targets. If present,
it wins on specifics. If missing, proceed with these standards and note
the gap in your summary — do not trigger skill generation mid-task.
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.
- 12d ago First seen · 75 lines · 45 tokens per session scan A f136aa4afea6
mav-bp-cicd is a skill published in the GitHub repository thermiteau/maverick (11 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 45 tokens to every session and 831 once invoked, about $0.0002 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.
managing-github-actions-secrets
Creates and updates GitHub Actions secrets for PostHog workflows. Use when adding a new CI secret, rotating an existing secret, wiring a workflow to an API token, package registry credential, deploy key, or any value referenced via ${{ secrets. }} in .github/workflows/.
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.