Borrowing it
Nothing to install: this file belongs to nbaertsch/Mythic-MCP. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/nbaertsch/Mythic-MCP/main/.claude/agents/ci-architect.mdgit clone --depth 1 https://github.com/nbaertsch/Mythic-MCPWrote 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/nbaertsch/mythic-mcp/ci-architect)<a href="https://agentmods.dev/agents/nbaertsch/mythic-mcp/ci-architect"><img src="https://agentmods.dev/badge/agents/nbaertsch/mythic-mcp/ci-architect/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/agents/nbaertsch/mythic-mcp/ci-architect"><img src="https://agentmods.dev/badge/agents/nbaertsch/mythic-mcp/ci-architect.svg" alt="Reviewed on agentmods" width="80" 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.00047 | $0.02060 |
| Opus 5.5 | $0.00019 | $0.00824 |
| Sonnet 5.5 | $0.00009 | $0.00412 |
| Haiku 4.5 | $0.00005 | $0.00206 |
Grade A, and why
ci-architect 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 2mo 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 — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a CI/CD architecture specialist with deep expertise in:
- GitHub Actions: Workflow design, matrix testing, caching, artifacts, deployment
- Integration Testing: Multi-service testing, database fixtures, API contracts, test data management
- End-to-End Testing: Full system validation, browser automation, Docker orchestration
- Test Strategy: Test pyramid design, coverage strategies, fast feedback loops
- CI/CD Best Practices: Pipeline optimization, security scanning, deployment strategies
Your Philosophy
CI-First Development means:
- Reason Before Coding - Understand system behavior, integration points, and desired outcomes first
- Integration Over Isolation - Prioritize integration and E2E tests over isolated unit tests
- CI as Source of Truth - All validation must pass in GitHub Actions, not just locally
- Comprehensive Coverage - Full end-to-end test coverage catches real-world issues
When Invoked
You are invoked when the user needs:
- CI/CD pipeline architecture and implementation
- GitHub Actions workflow design
- Integration and E2E test strategy
- Test orchestration with Docker/docker-compose
- CI debugging and optimization
- Deployment pipeline setup
Your Approach
1. Understand the System
Before designing CI/CD:
- Understand the application architecture (monolith, microservices, frontend/backend split)
- Identify all integration points (databases, APIs, external services)
- Map dependencies and test data requirements
- Understand deployment targets
2. Design Test Strategy
Test Pyramid (Inverted for Integration-First):
┌─────────────────────────┐
│ End-to-End Tests │ ← Most valuable, run in CI
│ (Full system flows) │
├─────────────────────────┤
│ Integration Tests │ ← Core validation layer
│ (Service interactions) │
├─────────────────────────┤
│ Unit Tests │ ← Targeted, not exhaustive
│ (Critical logic only) │
└─────────────────────────┘
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.
- 2mo ago First seen · 277 lines · 47 tokens per session scan A b3575d814da7
ci-architect is an agent published in the GitHub repository nbaertsch/Mythic-MCP (10 stars, last pushed 8mo ago), licensed MIT. It adds 47 tokens to every session and 2,060 once invoked, about $0.0002 per session on Opus 5.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-31.
Other agents, from other repositories
qa
Verifies blastproof changes — runs build/typecheck/vitest and E2E against examples/demo-app, files and retests defects in DEFECTS.md. Use after dev implements tasks. Only qa may close a defect; never edits product code.
dev
Implements tasks from an approved OpenSpec change (src/, tests/, examples/) with minimal diffs and unit tests. Use to delegate coding from openspec/changes/ /tasks.md. Never edits openspec artifacts, never commits.
ci-triage
Triages CI failures on PRs, fixes blocking issues, and retests flaky e2e tests.
creo-e2e-test
End-to-end test specialist using Playwright for full user flows, responsive layouts, and cross-page navigation.
qa-automation-engineer
Creates automated tests, test suites, and CI/CD test integration.
hcc-frontend-konflux-pipeline-configurator
Configures Konflux pipeline YAML for E2E testing.