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/solanabr/solana-ai-kit/setup-ci-cdgit clone --depth 1 https://github.com/solanabr/solana-ai-kitWrote 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/solanabr/solana-ai-kit/setup-ci-cd)<a href="https://agentmods.dev/commands/solanabr/solana-ai-kit/setup-ci-cd"><img src="https://agentmods.dev/badge/commands/solanabr/solana-ai-kit/setup-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.1 | $0.00012 | $0.02725 |
| Opus 5 | $0.00006 | $0.01362 |
| Sonnet 5 | $0.00002 | $0.00545 |
| Haiku 4.5 | $0.00001 | $0.00272 |
Grade A, and why
setup-ci-cd scanned grade A with 1 finding 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
sh -c "$(curl -sSfL https://release.solana.com/v${{ env.SOLANA_VERSION }}/install)" Copies of this mod
2 near-identical copies found in the catalogue:
- setup-ci-cd — 95% identical, 4 lines differ
- setup-ci-cd — 95% identical, 4 lines differ
How it starts
The opening of the file, as written. The whole thing — 442 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are setting up a CI/CD pipeline for Solana program development. Modern Solana development requires automated security checks on every commit.
Related Skills
- deployment.md - CI/CD patterns and workflows
- testing.md - Test automation
- security.md - Security automation
Overview
This command creates a GitHub Actions workflow that automatically:
- Builds programs with verifiable builds
- Runs comprehensive tests (unit, integration, fuzz)
- Performs security audits (cargo audit, clippy)
- Validates code formatting
- Generates security reports
Step 1: Create GitHub Actions Workflow
# Create .github/workflows directory
mkdir -p .github/workflows
# Create workflow file
cat > .github/workflows/solana-security.yml << 'EOF'
name: Solana Security Pipeline
on:
push:
branches: [ main, develop ]
pull_request:
branches: [ main ]
env:
SOLANA_VERSION: '2.1.0'
ANCHOR_VERSION: '0.31.1'
RUST_VERSION: '1.82.0'
jobs:
security-audit:
name: Security Audit
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Install Rust
uses: actions-rust-lang/setup-rust-toolchain@v1
with:
toolchain: ${{ env.RUST_VERSION }}
components: clippy, rustfmt
- name: Cache Cargo dependencies
uses: actions/cache@v4
with:
path: |
~/.cargo/bin/
~/.cargo/registry/index/
~/.cargo/registry/cache/
~/.cargo/git/db/
target/
key: ${{ runner.os }}-cargo-${{ hashFiles('**/Cargo.lock') }}
- name: Install Solana
run: |
sh -c "$(curl -sSfL https://release.solana.com/v${{ env.SOLANA_VERSION }}/install)"
echo "$HOME/.local/share/solana/install/active_release/bin" >> $GITHUB_PATH
- name: Install Anchor
run: |
cargo install --git https://github.com/coral-xyz/anchor --tag v${{ env.ANCHOR_VERSION }} anchor-cli --locked
- name: Format Check
run: cargo fmt --all -- --check
- name: Clippy Security Lints
run: |
cargo clippy --all-targets --all-features -- \
-W clippy::all \
-W clippy::pedantic \
-W clippy::unwrap_used \
-W clippy::expect_used \
-W clippy::arithmetic_side_effects \
-D warnings
- name: Cargo Audit
run: |
cargo install cargo-audit
cargo audit
- name: Build Programs
run: anchor build
- name: Run Tests
run: |
# Unit tests
cargo test
# Integration tests
anchor test --skip-deploy
- name: Security Report
if: always()
run: |
echo "## Security Audit Report" >> $GITHUB_STEP_SUMMARY
echo "- ✅ Format check passed" >> $GITHUB_STEP_SUMMARY
echo "- ✅ Clippy security lints passed" >> $GITHUB_STEP_SUMMARY
echo "- ✅ Cargo audit passed" >> $GITHUB_STEP_SUMMARY
echo "- ✅ All tests passed" >> $GITHUB_STEP_SUMMARY
verifiable-build:
name: Verifiable Build
runs-on: ubuntu-latest
if: github.event_name == 'push' && github.ref == 'refs/heads/main'
steps:
- uses: actions/checkout@v4
- name: Install Rust
uses: actions-rust-lang/setup-rust-toolchain@v1
with:
toolchain: ${{ env.RUST_VERSION }}
- name: Install Anchor
run: |
cargo install --git https://github.com/coral-xyz/anchor --tag v${{ env.ANCHOR_VERSION }} anchor-cli --locked
- name: Verifiable Build
run: anchor build --verifiable
- name: Upload Build Artifacts
uses: actions/upload-artifact@v4
with:
name: verifiable-build
path: |
target/deploy/*.so
target/idl/*.json
fuzz-testing:
name: Fuzz Testing
runs-on: ubuntu-latest
if: github.event_name == 'push'
steps:
- uses: actions/checkout@v4
- name: Install Rust
uses: actions-rust-lang/setup-rust-toolchain@v1
with:
toolchain: ${{ env.RUST_VERSION }}
- name: Install Trident
run: cargo install trident-cli
- name: Run Fuzz Tests
run: |
cd trident-tests
trident fuzz run --timeout 300
timeout-minutes: 10
continue-on-error: true
- name: Upload Fuzz Results
if: always()
uses: actions/upload-artifact@v4
with:
name: fuzz-results
path: trident-tests/hfuzz_workspace/
EOF
echo "✅ GitHub Actions workflow created: .github/workflows/solana-security.yml"
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.
- 6d ago First seen · 442 lines · 12 tokens per session scan A 0dcec5d71201
setup-ci-cd is a command published in the GitHub repository solanabr/solana-ai-kit (101 stars, last pushed 16d ago), licensed MIT. It adds 12 tokens to every session and 2,725 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
watch-ci
Monitor CI/CD pipeline and automatically fix failures. Watches GitHub Actions runs and applies fixes when tests fail.
gh-retry
Rerun all failed and cancelled workflow runs for a GitHub PR or all my PRs in a repo.
composite-actions
Generate, review, secure, and test composite GitHub Actions following best practices — full repo scaffold, interview-driven generation, PR creation on existing repos, SHA pinning, secrets-as-inputs, job summaries, and actionlint validation.
apex
APEX Methodology - The systematic Analyze-Plan-Execute-eLicit-eXamine approach for intelligent development. Reduces hallucination and defect risk through mandatory parallel research, self-review, and validation gates.
explain-architecture
Analyze and explain software architecture with ASCII diagrams and pattern detection. Creates visual representations of system design.
prompt
Create or optimize prompts using best practices.