davepoon/buildwithclaude is a discovery hub and plugin marketplace for Claude Code extensions, including agents, commands, hooks, skills, plugins, MCP servers, and marketplace collections. Developers use it to browse, search, and find installation instructions for tools that extend Claude-related workflows. Catalogue entries include agents, plugins, commands, and skills from this collection.
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 commands/davepoon/buildwithclaude/ci-setupgit clone --depth 1 https://github.com/davepoon/buildwithclaudeWrote 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/commands/davepoon/buildwithclaude/ci-setup)<a href="https://agentmods.dev/commands/davepoon/buildwithclaude/ci-setup"><img src="https://agentmods.dev/badge/commands/davepoon/buildwithclaude/ci-setup.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.00004 | $0.01993 |
| Opus 5 | $0.00002 | $0.00996 |
| Sonnet 5 | $0.00001 | $0.00399 |
| Haiku 4.5 | $0.00000 | $0.00199 |
Grade A, and why
ci-setup 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 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.
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 — 315 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI/CD Setup Command
Setup continuous integration pipeline
Instructions
Follow this systematic approach to implement CI/CD: $ARGUMENTS
-
Project Analysis
- Identify the technology stack and deployment requirements
- Review existing build and test processes
- Understand deployment environments (dev, staging, prod)
- Assess current version control and branching strategy
-
CI/CD Platform Selection
- Choose appropriate CI/CD platform based on requirements:
- GitHub Actions: Native GitHub integration, extensive marketplace
- GitLab CI: Built-in GitLab, comprehensive DevOps platform
- Jenkins: Self-hosted, highly customizable, extensive plugins
- CircleCI: Cloud-based, optimized for speed
- Azure DevOps: Microsoft ecosystem integration
- AWS CodePipeline: AWS-native solution
- Choose appropriate CI/CD platform based on requirements:
-
Repository Setup
- Ensure proper
.gitignoreconfiguration - Set up branch protection rules
- Configure merge requirements and reviews
- Establish semantic versioning strategy
- Ensure proper
-
Build Pipeline Configuration
GitHub Actions Example:
name: CI/CD Pipeline on: push: branches: [ main, develop ] pull_request: branches: [ main ] jobs: test: runs-on: ubuntu-latest steps: - uses: actions/checkout@v3 - name: Setup Node.js uses: actions/setup-node@v3 with: node-version: '18' cache: 'npm' - run: npm ci - run: npm run test - run: npm run buildGitLab CI Example:
stages: - test - build - deploy test: stage: test script: - npm ci - npm run test cache: paths: - node_modules/ -
Environment Configuration
- Set up environment variables and secrets
- Configure different environments (dev, staging, prod)
- Implement environment-specific configurations
- Set up secure secret management
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 First seen · 315 lines · 4 tokens per session scan A 5a19ce695f62
ci-setup is a command published in the GitHub repository davepoon/buildwithclaude (3,415 stars, last pushed today), licensed MIT. It adds 4 tokens to every session and 1,993 once invoked, about $0.0000 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-05.
Other commands, from other repositories
test-pr-docker
Test PR with Docker image build workflow.
status
Check if remote Docker environment needs updating.
ops-vercel
Command "ops-vercel" from christopherlouet/claude-base, covering ops-vercel agent (pointer), context, delegate to the vendor toolkit and related agents.
work-flow-release
Complete workflow to prepare and publish a release.
work-flow-launch
Technical workflow to develop and launch a product, from setup to go-live.
ops-ci-fix
Diagnose and repair failing CI/CD pipelines.