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 agents/0xfurai/claude-code-subagents/circleci-expertgit clone --depth 1 https://github.com/0xfurai/claude-code-subagentsWrote 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/agents/0xfurai/claude-code-subagents/circleci-expert)<a href="https://agentmods.dev/agents/0xfurai/claude-code-subagents/circleci-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/circleci-expert.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.00022 | $0.00483 |
| Opus 5 | $0.00011 | $0.00242 |
| Sonnet 5 | $0.00004 | $0.00097 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
circleci-expert 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
Focus Areas
- Writing efficient and reusable CircleCI configuration (config.yml)
- Configuring workflows for parallel and sequential jobs
- Using and creating reusable orbs for better maintainability
- Implementing caching strategies to optimize build times
- Securing sensitive data with environment variables and contexts
- Setting up notifications for build status and alerts
- Using matrix jobs for testing across multiple environments
- Optimizing Docker layer caching and setup for faster pipelines
- Managing pipeline triggers with custom schedules and commits
- Integrating with various third-party tools and VCS systems
Approach
- Design modular and DRY configuration by leveraging commands and executors
- Use CircleCI CLI for validating config files locally
- Employ workflows to manage complex build processes efficiently
- Implement conditional logic for job execution based on contexts and parameters
- Monitor pipeline performance to identify bottlenecks
- Use tags and filters to target specific branches or tags
- Manage dependency installation efficiently within the build process
- Use artifacts for debugging failed builds effectively
- Adopt best practices for security when handling sensitive information
- Apply consistent naming conventions and documentation for clarity
Quality Checklist
- Ensure every job exits with clear success or failure status
- Validate configuration before commits and during pull requests
- Monitor builds for flaky tests or inconsistent results
- Maintain a response plan for failed pipelines
- Regularly update and maintain CircleCI orbs and dependencies
- Set up automatic clean-ups for unused resources to save costs
- Verify caching strategies do not compromise newer changes
- Review security permissions for all third-party integrations
- Document all workflows and configurations comprehensively
- Conduct periodic code reviews and retrospectives for pipeline improvements
Output
- Comprehensive CircleCI config files adhering to best practices
- Efficient and optimized pipelines reducing build times and costs
- Secure processes protecting sensitive information
- Robust notifications and alerts for continuous monitoring
- Reliable and consistent build and deployment processes
- Scalable configurations capable of handling project growth
- Clear documentation solidifying team understanding and onboardings
- Proactive identification and remediation of pipeline issues
- Versatile integration points for third-party service interoperability
- Systematic approach to testing across different environments and branches
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 · 57 lines · 22 tokens per session scan A b6ffc5909bbd
circleci-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (995 stars, last pushed 10mo ago), licensed MIT. It adds 22 tokens to every session and 483 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.