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 G1Joshi/Agent-Skills --skill circlecigit clone --depth 1 https://github.com/G1Joshi/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/g1joshi/agent-skills/circleci)<a href="https://agentmods.dev/skills/g1joshi/agent-skills/circleci"><img src="https://agentmods.dev/badge/skills/g1joshi/agent-skills/circleci.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.00015 | $0.00419 |
| Opus 5 | $0.00008 | $0.00210 |
| Sonnet 5 | $0.00003 | $0.00084 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
circleci 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 4d 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.
What it actually says
CircleCI
CircleCI is a cloud-native CI/CD platform focused on speed and parallelism. In 2025, Dynamic Config and Orbs are the key drivers of efficiency.
When to Use
- Speed: Best-in-class caching, test splitting, and parallelism.
- Complexity: Dynamic Configuration allows pipelines to change structure based on changed files (Monorepo support).
- Compliance: FedRAMP / SOC2 compliance is strong.
Quick Start
# .circleci/config.yml
version: 2.1
orbs:
node: circleci/[email protected]
jobs:
build:
executor: node/default
steps:
- checkout
- node/install-packages:
pkg-manager: npm
- run: npm run test
workflows:
build-and-test:
jobs:
- build
Core Concepts
Orbs
Shareable packages of config. circleci/[email protected] encapsulates 500 lines of bash into one line of YAML.
Test Splitting
Intelligently divides test files across N parallel nodes to reduce build time from 30m to 3m.
Dynamic Config (2025)
A setup workflow generates the real workflow. Allows logic like "If only /backend changed, don't run frontend tests".
Best Practices (2025)
Do:
- Use Dynamic Config: Essential for monorepos to save credits.
- Use Contexts: Securely share secrets across projects (e.g.,
AWS_CREDS). - Use
dockerexecutor: It is faster thanmachineexecutor for most tasks.
Don't:
- Don't reinvent the wheel: Check the Orb Registry before writing custom commands.
References
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.
- 4d ago First seen · 67 lines · 15 tokens per session scan A a52ece022132
circleci is a skill published in the GitHub repository G1Joshi/Agent-Skills (12 stars, last pushed 6mo ago), licensed MIT. It adds 15 tokens to every session and 419 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-09-03.
Other skills, from other repositories
ci-cd-and-automation
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
browser-testing-with-devtools
Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be…
Flaky Test Quarantine
Detect, quarantine, and systematically fix flaky tests with automated retry analysis, root cause categorization, and CI pipeline integration for test reliability.
Checkly Monitoring as Code
Teach agents to build synthetic monitoring as code with Checkly, including Playwright browser checks, API checks, alerting, and CI deploy workflows.
CI Test Sharding Parallelization
Teach agents to shard and parallelize Playwright, Jest, and pytest suites in CI to reduce wall-clock time while merging reports reliably.
Advanced Chaos Engineering
Advanced chaos engineering patterns using Chaos Monkey, Litmus, and Gremlin for testing distributed system resilience under failure conditions.