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 jonlwowski012/copilot-agent-factory --skill ci-pipelinegit clone --depth 1 https://github.com/jonlwowski012/copilot-agent-factoryWrote 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/jonlwowski012/copilot-agent-factory/ci-pipeline)<a href="https://agentmods.dev/skills/jonlwowski012/copilot-agent-factory/ci-pipeline"><img src="https://agentmods.dev/badge/skills/jonlwowski012/copilot-agent-factory/ci-pipeline/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/jonlwowski012/copilot-agent-factory/ci-pipeline"><img src="https://agentmods.dev/badge/skills/jonlwowski012/copilot-agent-factory/ci-pipeline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00013 | $0.02520 |
| Opus 5 | $0.00006 | $0.01260 |
| Sonnet 5 | $0.00003 | $0.00504 |
| Haiku 4.5 | $0.00001 | $0.00252 |
Grade A, and why
ci-pipeline 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 — 527 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: CI/CD Pipeline
When to Use This Skill
This skill activates when you need to:
- Understand the project's CI/CD setup
- Debug failing CI/CD pipelines
- Fix workflow errors
- Add or modify CI checks
- Understand why checks are failing on your PR
Prerequisites
- Basic understanding of CI/CD concepts
- Access to repository (to view workflow runs)
- Understanding of project's tech stack
Step-by-Step Workflow
Step 1: Identify CI/CD Platform
Check for CI configuration files:
# GitHub Actions
.github/workflows/*.yml
# GitLab CI
.gitlab-ci.yml
# CircleCI
.circleci/config.yml
# Travis CI
.travis.yml
# Jenkins
Jenkinsfile
# Azure Pipelines
azure-pipelines.yml
Step 2: View CI Pipeline Status
GitHub Actions (via CLI):
# Install GitHub CLI if needed
# https://cli.github.com/
# List recent workflow runs
gh run list
# View specific run
gh run view <run-id>
# Watch a running workflow
gh run watch
GitHub Actions (via Web):
- Go to repository on GitHub
- Click "Actions" tab
- Select workflow run
- View job details and logs
Step 3: Understand Common CI Workflows
Typical CI Pipeline Stages
# .github/workflows/ci.yml example
name: CI
on: [push, pull_request]
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- name: Setup
# Install dependencies
- name: Lint
# Run linter
- name: Test
# Run tests
- name: Build
# Build project
Common stages:
- Checkout - Clone repository code
- Setup - Install language/dependencies
- Lint - Check code style
- Test - Run test suite
- Build - Compile/build project
- Deploy - Deploy to environment (optional)
Step 4: Debug Failing CI Checks
Step 4a: Identify Which Check Failed
Look at PR checks:
- ✅ Green check - Passed
- ❌ Red X - Failed
- 🟡 Yellow dot - Running
- ⚪ Gray circle - Pending
Click on failed check to see:
- Job name
- Failure step
- Error message
- Logs
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 · 527 lines · 13 tokens per session scan A 05e783aea685
ci-pipeline is a skill published in the GitHub repository jonlwowski012/copilot-agent-factory (16 stars, last pushed 10d ago), licensed MIT. It adds 13 tokens to every session and 2,520 once invoked, about $0.0001 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
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.