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 flurdy/agent-skills --skill circleci-statusgit clone --depth 1 https://github.com/flurdy/agent-skillsWrote 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/flurdy/agent-skills/circleci-status)<a href="https://agentmods.dev/skills/flurdy/agent-skills/circleci-status"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/circleci-status.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.00041 | $0.00789 |
| Opus 5 | $0.00020 | $0.00394 |
| Sonnet 5 | $0.00008 | $0.00158 |
| Haiku 4.5 | $0.00004 | $0.00079 |
Grade A, and why
circleci-status 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 today.
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.
allowed-tools: "Bash(~/.agents/skills/circleci-status/scripts/status.sh:*), Bash(~/.agents/skills/circleci-status/scripts/logs.sh:*), Bash(gh api:*), Bash(gh auth status:*), Bash(git config:*), Bash(git branch:*), Bash(g How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CircleCI Status
Check the latest CircleCI pipeline/workflow status for the current GitHub repository, with optional failed job logs.
Authentication
- Basic GitHub commit status/check-run summaries use
ghwhen authenticated. - CircleCI pipeline/workflow/job details use
CIRCLECI_TOKENwhen already set, otherwisesecret-api-key lookup circleci "$SECRET_API_KEY_PROJECT". - CircleCI project slug is derived from
origin:gh/{owner}/{repo}.
Store the token once and expose only its non-secret project selector:
secret-api-key store circleci flurdy
export SECRET_API_KEY_PROJECT=flurdy
Usage
/circleci-status # Summarise latest status for current branch/HEAD
/circleci-status logs # Show latest failed job logs for current branch
/circleci-status main # Summarise latest CircleCI pipeline for branch main
/circleci-status logs main
Instructions
Always run the helper scripts fresh; never reuse prior status output.
Status mode
For no argument, or an argument other than logs, run:
~/.agents/skills/circleci-status/scripts/status.sh {optional-branch-or-ref}
Rollout watchers may pass a second exact revision argument. In that mode the helper selects only the matching branch pipeline and uses the same revision for GitHub status/check fallbacks:
~/.agents/skills/circleci-status/scripts/status.sh {branch} {sha}
Render:
## CircleCI status — {repo} `{branch}`
- GitHub commit status: {state}
- GitHub check runs: {counts by conclusion/status}
- CircleCI: {workflow statuses or token-missing note}
If ---CIRCLECI-STATUS--- is NO_TOKEN, say:
CircleCI API details unavailable: configure
SECRET_API_KEY_PROJECTand its CircleCI key. GitHub commit/check status above may still show CircleCI's reported state.
If GitHub status includes CircleCI contexts with target_url, include links for failing/pending contexts.
Logs mode
For logs as the first argument, run:
~/.agents/skills/circleci-status/scripts/logs.sh {optional-branch}
What ships with it
3 files 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.
- today Changed · +7 lines e49ed820cbf2
- 8d ago First seen · 90 lines · 41 tokens per session scan A 0df2d567daf6
circleci-status is a skill published in the GitHub repository flurdy/agent-skills (9 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 789 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-31.
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.