A command that creates a GitHub Actions workflow for Solana programs. GitHub Actions runs build, test, formatting, and security tasks automatically when code is pushed or submitted for review.

Use it to build Solana programs, run unit, integration, and fuzz tests, check Rust code with cargo audit and clippy, validate formatting, and produce security reports.

It moves repeated checks into every commit and pull request, helping find broken builds, test failures, formatting issues, and common security problems early.

setup-ci-cd — Command for Claude Code by solanabr/solana-ai-kit

Install

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.

Clone the repo

git clone --depth 1 https://github.com/solanabr/solana-ai-kit

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/solanabr/solana-ai-kit/setup-ci-cd/github.svg)](https://agentmods.dev/commands/solanabr/solana-ai-kit/setup-ci-cd)

Your own site

<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/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.

Your own site · 80×15

<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="Reviewed on agentmods" width="80" height="20"></a>

Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 753 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00018	$0.00753
Opus 5.5	$0.00007	$0.00301
Sonnet 5.5	$0.00004	$0.00151
Haiku 4.5	$0.00002	$0.00075

Measured 25d ago against content hash 7812d72c53ad, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

setup-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 25d 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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

setup-ci-cd — 95% identical, 447 lines differ
setup-ci-cd — 95% identical, 447 lines differ

.claude/commands/setup-ci-cd.md · 21 lines

How it starts

The opening of the file, as written. The whole thing — 21 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Create a GitHub Actions pipeline for this repo's programs, adapted to what the repo actually uses (Anchor or native, where tests live, package manager). Workflow and deploy-stage patterns: deployment.md. Test layers: testing.md.

Steps

Write .github/workflows/solana-security.yml, triggered on pull requests and on pushes to main, with these jobs:
- lint: cargo fmt --all -- --check and cargo clippy --all-targets -- -D warnings. Optionally tighten the program crates' library targets with -W clippy::arithmetic_side_effects -W clippy::unwrap_used -W clippy::expect_used, scoped to --lib so tests can still unwrap.
- build: anchor build (Anchor) or cargo build-sbf (native/Pinocchio). Install toolchains at the versions pinned in Anchor.toml [toolchain] or rust-toolchain.toml instead of hardcoding them: the Solana CLI from https://release.anza.xyz/<version>/install (not the old release.solana.com), Anchor through avm. Cache ~/.cargo and target/.
- test, after the build, since LiteSVM and Mollusk tests load the .so from target/deploy/: cargo test for the Rust tests. anchor test defaults to Surfpool in Anchor 1.x, so either install the surfpool CLI on the runner or run anchor test --validator legacy to use solana-test-validator. If trident-tests/ exists, add a time-boxed, non-blocking Trident fuzz job.
- audit: cargo audit for RustSec advisories, or cargo deny check for advisories plus licenses and banned crates. License policy belongs in cargo-deny's deny.toml; audit.toml has no license settings.
- verifiable build, on pushes to main and release tags: anchor build --verifiable (or solana-verify build for native programs), uploading the verifiable .so (target/verifiable/ for Anchor) and target/idl/*.json as artifacts.
Add .github/dependabot.yml with weekly cargo and github-actions updates (plus npm when there is a client), and a short .github/PULL_REQUEST_TEMPLATE.md checklist that points at /diff-review, /audit-solana, /profile-cu and the verifiable build instead of copying the house rules. A local .git/hooks/pre-commit for human contributors is optional; Claude sessions already get the kit's git commit hook.
Deploy jobs are optional. Keep them to devnet, behind a GitHub environment with required reviewers. Store the deployer keypair JSON as an environment secret, write it to a temp file at runtime, and never echo it or upload it as an artifact. Mainnet upgrades stay out of automatic CI (buffer plus multisig; see deployment.md).

Read the full file on GitHub · 21 lines

Changes

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.

25d ago Changed · -421 lines · +6 tokens per session 7812d72c53ad
26d ago Changed 96846789a683
1mo ago First seen · 442 lines · 12 tokens per session scan A 0dcec5d71201

Subscribe to this mod's changes

setup-ci-cd is a command published in the GitHub repository solanabr/solana-ai-kit (104 stars, last pushed 26d ago), licensed MIT. It adds 18 tokens to every session and 753 once invoked, about $0.0001 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-30.

CI and CD Claude Code DevOps and cloud Security claude-agent claude-commands claude-md claude-skills claude-subagents

setup-ci-cd

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

Copies of this mod

How it starts

Steps

What this file has done since we first saw it

Other commands, from other repositories

watch-ci

gh-retry

apex

explain-architecture

prompt

design-audit