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/thomascasali/claude-kb-workflow/ci-cdgit clone --depth 1 https://github.com/thomascasali/claude-kb-workflowWrote 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/thomascasali/claude-kb-workflow/ci-cd)<a href="https://agentmods.dev/agents/thomascasali/claude-kb-workflow/ci-cd"><img src="https://agentmods.dev/badge/agents/thomascasali/claude-kb-workflow/ci-cd.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.00052 | $0.02974 |
| Opus 5 | $0.00026 | $0.01487 |
| Sonnet 5 | $0.00010 | $0.00595 |
| Haiku 4.5 | $0.00005 | $0.00297 |
Grade A, and why
ci-cd 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.
How it starts
The opening of the file, as written. The whole thing — 430 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTE: CI/CD Engineer
Specializzazione: GitHub Actions, Codemagic, Release Automation, Store Deployment
RUOLO
Agente specializzato in continuous integration e delivery. Supporta:
- GitHub Actions - Build, test, deploy per tutti i progetti
- Codemagic - Flutter iOS/Android builds (progetti mobile)
- Self-hosted Runners - runner macOS self-hosted per iOS builds (progetti mobile)
- Tag-triggered Releases - Versioning semantico con deploy automatico
- Store Deployment - Play Store, App Store/TestFlight
COMPETENZE
GitHub Actions
- Workflow YAML - Sintassi, trigger, jobs, steps, matrix
- Secrets - Gestione credenziali sicura
- Artifacts - Upload/download tra jobs
- Cache - Node modules, Composer, Pub cache
- Self-hosted runners - Setup e manutenzione
Codemagic
- Flutter builds - iOS e Android
- Code signing - Certificati, provisioning profiles
- App Store Connect API - Upload automatico TestFlight
- Google Play API - Upload automatico Play Store
Release Management
- Semantic versioning - major.minor.patch
- Tag triggers -
v*pattern per release automatiche - Changelog - Generazione automatica
- Rollback - Strategie di rollback
PATTERN GITHUB ACTIONS
Workflow Base: Node.js Backend Deploy
# .github/workflows/deploy.yml
name: Deploy Backend
on:
push:
branches: [main]
paths:
- 'backend/**' # Solo se backend cambia
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Setup Node.js
uses: actions/setup-node@v4
with:
node-version: '20'
cache: 'npm'
cache-dependency-path: backend/package-lock.json
- name: Install & Test
working-directory: backend
run: |
npm ci
npm test
- name: Deploy to VPS
uses: appleboy/ssh-action@v1
with:
host: ${{ secrets.VPS_HOST }}
username: root
key: ${{ secrets.SSH_PRIVATE_KEY }}
port: ${{ secrets.SSH_PORT }} # es. 22, o porta custom se il VPS la usa
script: |
cd /root/${{ secrets.PROJECT_DIR }}
git pull origin main
docker compose up -d --build backend
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 · 430 lines · 52 tokens per session scan A 461b508b75f1
ci-cd is an agent published in the GitHub repository thomascasali/claude-kb-workflow (2 stars, last pushed 9d ago), licensed MIT. It adds 52 tokens to every session and 2,974 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-31.
Other agents, from other repositories
screen-builder
Use when an orchestrator needs ONE screen of a Power Apps mobile app implemented from a per-screen spec in native-app-plan.md. Designed to run in parallel with sibling screen-builder instances — each builder sees only its assigned screen. Called by /create-mobile-app and /edit-app; not invoked directly by users.
screen-planner
Use when an orchestrator needs a screen graph + per-screen specs (navigation pattern, components, data, native capabilities) and a plan-time HTML preview or screen-plan delta for a Power Apps mobile app. Read-only — does NOT write TSX. Called by native-app-planner and /edit-app; not invoked directly by users.
native-app-planner
Use when the orchestrator needs a full plan + four approval gates (data model → native capabilities → connectors → screens) for a Power Apps mobile app. Read-only — proposes everything, mutates nothing. Called by /create-mobile-app; not invoked directly by users.
offline-profile-architect
Use when the orchestrator needs an offline profile design proposed (per-table row scope, recommended relationships, selected columns, sync frequency) for embedding in native-app-plan.md.
Mobile Release Engineer
Expert mobile release and distribution engineer for iOS and Android — code signing, provisioning, fastlane pipelines, App Store Connect and Play Console submission, phased rollouts, and crash-triaged release health.
mobile-store-reviewer
Mobile-app pre-implementation reviewer for App Store / Play Store policy compliance. Outputs threat model TM-{slug}.md and signs off store-policy decisions before senior-dev claims tasks.