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/drn/dots/ci-investigatenpx skills add drn/dots --skill ci-investigategit clone --depth 1 https://github.com/drn/dotsWrote 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/drn/dots/ci-investigate)<a href="https://agentmods.dev/skills/drn/dots/ci-investigate"><img src="https://agentmods.dev/badge/skills/drn/dots/ci-investigate.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 | $0.00051 | $0.01361 |
| Opus 5 | $0.00026 | $0.00681 |
| Sonnet 5 | $0.00010 | $0.00272 |
| Haiku 4.5 | $0.00005 | $0.00136 |
Grade A, and why
ci-investigate 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 5d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI Failure Investigator
Investigate flaky CI failures across multiple workflow runs to identify patterns, categorize root causes, and propose targeted fixes.
Arguments
$ARGUMENTS- Optional: job name filter, number of runs to check, or branch name. Examples: "test-core-rspec", "--runs 10", "master"
If no arguments are provided, investigate the most recent failing workflow on the current branch.
Context
- Current branch: !
git branch --show-current - Repo remote: !
git remote get-url origin 2>/dev/null | head -1 - CI config: !
find . -maxdepth 2 \( -name ".circleci" -o -name ".github" \) -type d 2>/dev/null | head -5 - CircleCI config snippet: !
head -30 .circleci/config.yml 2>/dev/null | head -30
Instructions
Investigate CI failures by fetching multiple workflow runs, extracting test results, and categorizing failure patterns.
Step 1: Determine Scope
Parse $ARGUMENTS for:
- Job name filter (e.g., "test-core-rspec") -- only analyze jobs matching this name
- Run count (e.g., "--runs 10") -- how many recent runs to check (default: 5, max: 15)
- Branch -- which branch to investigate (default: current branch from context above)
Derive the project slug from the git remote URL. For GitHub repos, format is "gh/org/repo".
Report the scope to the user before proceeding:
- Project slug
- Branch
- Job filter (if any)
- Number of runs to fetch
Step 2: Fetch Recent Workflow Runs
Detect the CI provider from the context above and use the appropriate tools.
CircleCI (if .circleci/ exists): Use ToolSearch to find available CircleCI MCP tools (search "circleci"). Then:
- Fetch recent pipelines for the project slug and branch
- For each pipeline, get its workflows
- For each workflow, get jobs and their statuses
- Filter to failed jobs (and optionally by job name from Step 1)
GitHub Actions (if .github/workflows/ exists): Use the gh CLI:
gh run list --branch {branch} --limit {N}to get recent runsgh run view {run_id}to get job detailsgh run view {run_id} --log-failedto get failure output
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.
- 5d ago First seen · 141 lines · 51 tokens per session scan A 8b193d2f7d34
ci-investigate is a skill published in the GitHub repository drn/dots (23 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 1,361 once invoked, about $0.0003 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…
ci-security-scanning-with-strix
Add security scanning to CI/CD with Strix — GitHub Actions, GitLab CI, or any pipeline — so every pull request gets a diff-scoped AI pentest that blocks vulnerable code before it merges, with results as PR comments and SARIF uploaded to code scanning. Covers both the self-hosted open-source CLI (runs in your runner)…
chinese-git-workflow
国内 Git 平台配置参考——Gitee、Coding.net、极狐 GitLab、CNB 的 SSH/HTTPS/凭据/CI 接入差异与镜像同步配置。仅在用户显式 /chinese-git-workflow 时调用，不要根据上下文自动触发。.
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…
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…
desktop-principles
Desktop-specific UX principles - hover states, pointer precision, keyboard shortcuts, multi-window, focus management. Covers macOS, Windows, Linux, web desktop.