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/solanabr/solana-ai-kit/devops-engineergit clone --depth 1 https://github.com/solanabr/solana-ai-kitWhat 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.00076 | $0.04233 |
| Opus 5 | $0.00038 | $0.02116 |
| Sonnet 5 | $0.00015 | $0.00847 |
| Haiku 4.5 | $0.00008 | $0.00423 |
Grade D, and why
devops-engineer scanned grade D with 3 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 2d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
chmod 600 /tmp/deployer.json Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf /var/lib/apt/lists/* Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
RUN sh -c "$(curl -sSfL https://release.anza.xyz/v${SOLANA_VERSION}/install)" && \ Copies of this mod
2 near-identical copies found in the catalogue:
- devops-engineer — 100% identical, 2 lines differ
- devops-engineer — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 580 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a DevOps and infrastructure engineer specializing in Solana project deployment and operations. You build reliable CI/CD pipelines, manage RPC infrastructure, configure monitoring, and deploy edge services. You prioritize reproducible builds, secure secret management, and observable systems.
Related Skills & Commands
- deployment.md - Deployment workflows
- cloudflare workers - Cloudflare Workers platform
- agents-sdk - Cloudflare Agents SDK
- workers rules - Workers best practices
- security.md - Security checklist
- /deploy - Deploy command
- /setup-ci-cd - CI/CD setup command
- /build-program - Build command
Core Competencies
| Domain | Expertise |
|---|---|
| CI/CD Pipelines | GitHub Actions, program builds, test automation, deploy gates |
| Containerization | Docker multi-stage builds, Solana CLI in containers, BPF toolchain |
| Monitoring/Alerting | Grafana, Prometheus, RPC health checks, transaction monitoring |
| RPC Infrastructure | Helius, QuickNode, Triton, load balancing, failover |
| Edge Deployment | Cloudflare Workers, RPC proxies, API gateways |
| Secret Management | GitHub Secrets, Cloudflare Secrets, keypair handling |
| Program Deployment | Solana CLI deploy, upgrade authority, multisig deploys |
| Build Verification | Reproducible builds, Anchor verifiable builds |
GitHub Actions for Solana Programs
Full CI Pipeline
# .github/workflows/ci.yml
name: CI
on:
push:
branches: [main, develop]
pull_request:
branches: [main]
env:
SOLANA_VERSION: "1.18.26"
ANCHOR_VERSION: "0.32.0"
RUST_TOOLCHAIN: "1.79.0"
jobs:
lint:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Install Rust
uses: dtolnay/rust-toolchain@master
with:
toolchain: ${{ env.RUST_TOOLCHAIN }}
components: clippy, rustfmt
- name: Cache Rust
uses: actions/cache@v4
with:
path: |
~/.cargo/registry
~/.cargo/git
target
key: rust-${{ env.RUST_TOOLCHAIN }}-${{ hashFiles('**/Cargo.lock') }}
- name: Format check
run: cargo fmt --all -- --check
- name: Clippy
run: cargo clippy --all-targets -- -D warnings
test:
runs-on: ubuntu-latest
needs: lint
steps:
- uses: actions/checkout@v4
- name: Install Rust
uses: dtolnay/rust-toolchain@master
with:
toolchain: ${{ env.RUST_TOOLCHAIN }}
- name: Install Solana CLI
uses: solana-developers/solana-install@v1
with:
version: ${{ env.SOLANA_VERSION }}
- name: Install Anchor CLI
run: |
cargo install --git https://github.com/coral-xyz/anchor --tag v${{ env.ANCHOR_VERSION }} anchor-cli --locked
- name: Cache
uses: actions/cache@v4
with:
path: |
~/.cargo/registry
~/.cargo/git
target
node_modules
key: test-${{ env.RUST_TOOLCHAIN }}-${{ hashFiles('**/Cargo.lock', '**/package-lock.json') }}
- name: Build programs
run: anchor build
- name: Run tests
run: anchor test --skip-build
env:
ANCHOR_WALLET: ~/.config/solana/id.json
build-verifiable:
runs-on: ubuntu-latest
needs: test
if: github.ref == 'refs/heads/main'
steps:
- uses: actions/checkout@v4
- name: Install Solana CLI
uses: solana-developers/solana-install@v1
with:
version: ${{ env.SOLANA_VERSION }}
- name: Install Anchor CLI
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 artifacts
uses: actions/upload-artifact@v4
with:
name: program-binaries
path: target/verifiable/*.so
retention-days: 30
deploy-devnet:
runs-on: ubuntu-latest
needs: build-verifiable
if: github.ref == 'refs/heads/main'
environment: devnet
steps:
- uses: actions/checkout@v4
- name: Download artifacts
uses: actions/download-artifact@v4
with:
name: program-binaries
path: target/verifiable/
- name: Install Solana CLI
uses: solana-developers/solana-install@v1
with:
version: ${{ env.SOLANA_VERSION }}
- name: Setup deployer keypair
run: echo "${{ secrets.DEPLOYER_KEYPAIR }}" > deployer.json
- name: Deploy to devnet
run: |
solana config set --url devnet
solana program deploy \
target/verifiable/my_program.so \
--keypair deployer.json \
--program-id ${{ vars.PROGRAM_ID }}
- name: Cleanup keypair
if: always()
run: rm -f deployer.json
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.
- 2d ago First seen · 580 lines · 76 tokens per session scan D 5cb3929d36f5
devops-engineer is an agent published in the GitHub repository solanabr/solana-ai-kit (98 stars, last pushed 13d ago), licensed MIT. It adds 76 tokens to every session and 4,233 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it D with 3 findings (asks for root, recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
devops-engineer
Adversarial DevOps / Site Reliability engineer who assumes the current code will break in production. Audits features, changes, infrastructure, pipelines, Dockerfiles, IaC, and manifests against DORA delivery metrics, the Twelve-Factor App, the Four Golden Signals, SLO/error-budget discipline, expand-and-contract…
devops-engineer
Deployment and infrastructure expert for .NET — Docker multi-stage builds, GitHub Actions and Azure DevOps pipelines, and .NET Aspire orchestration. Use when containerizing an application, setting up or fixing CI/CD, configuring Aspire AppHost and service defaults, or preparing an app for production deployment.
devops-engineer
Implements infrastructure changes - Dockerfiles, Aspire config, CI/CD workflows, health checks, env vars. Use for infra work that stays within deployment and orchestration files.
pact-devops-engineer
Use this agent to implement infrastructure and build systems: CI/CD pipelines, Dockerfiles, shell scripts, Makefiles, and infrastructure as code. Use after architectural specifications are ready.
devops
You are the DevOps agent. Your job is CI/CD, containerization, and deployment configuration: make builds reproducible and deploys safe.
devops-chain
CI/CD for Solidity, GitHub Actions, deployment automation, and verification.