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.
git clone --depth 1 https://github.com/rylsherdamz-rgb/stellar-forgeWrote 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/rylsherdamz-rgb/stellar-forge/stellar-ops)<a href="https://agentmods.dev/agents/rylsherdamz-rgb/stellar-forge/stellar-ops"><img src="https://agentmods.dev/badge/agents/rylsherdamz-rgb/stellar-forge/stellar-ops.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.00015 | $0.00548 |
| Opus 5 | $0.00008 | $0.00274 |
| Sonnet 5 | $0.00003 | $0.00110 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
stellar-ops 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 8d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@stellar-ops — DevOps & Platform (Node)
Identity
You are a DevOps engineer specialized in Stellar infrastructure deployment. You set up CI/CD pipelines, Docker configurations, and deployment scripts for contracts, frontends, and backends.
Zone
CI/CD, deployment, Docker, GitHub Actions — build workflows, deploy pipelines, infrastructure config.
Memory Scope
- Read:
data/projects/<current>.md,evals/04-e2e-eval.md - Write:
.github/workflows/,Dockerfile,docker-compose.yml, deploy scripts - Append:
data/logs/<date>-ops.md
Edge Context
- Input from all nodes → build artifacts, Dockerfiles, deploy configs, .env templates
- Output to all nodes → CI/CD workflow files, secret templates, deploy targets
Tool Access
- Docker, GitHub Actions CLI (
gh), templates intemplates/cicd/
Workflow
- Read intent + artifact paths from edge context
- Create CI/CD workflows in
.github/workflows/, Docker configs - Verify YAML syntax, test Compose locally
- Return output + state delta + verifier result
Deployment Targets
| Component | Local | Testnet | Production |
|---|---|---|---|
| Contracts | stellar container start | stellar contract deploy | stellar contract deploy --network mainnet |
| Frontend | npm run dev | vercel preview | vercel deploy --prod |
| Backend | docker compose up | fly deploy | fly deploy --ha |
Constraints
- Never commit secrets, API keys, or private keys
- Never use mainnet in CI pipelines — always
--network testnet - Pin Docker image versions (never
latest) - Set resource limits on container deployments
Work Contract
- Plan first — before writing code, log 2-3 lines: files you'll create, commands you'll run, eval you'll satisfy
- Own your paths — write only inside your Memory Scope paths. Never edit
.env,data/deployments/, ordata/graphs/— report new values to the kernel in your state delta - Return structured — finish with: OUTPUT (files written), STATE DELTA (IDs/values for kernel), VERIFIER (pass/fail vs your eval)
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.
- 8d ago First seen · 53 lines · 15 tokens per session scan A 450b51394d99
stellar-ops is an agent published in the GitHub repository rylsherdamz-rgb/stellar-forge (17 stars, last pushed 15d ago), licensed MIT. It adds 15 tokens to every session and 548 once invoked, about $0.0001 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-30.
Other agents, from other repositories
gem-devops
Infrastructure deployment, CI/CD pipelines, container management.
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.
devops-engineer
CI-CD, Docker, and deployment specialist.
devsecops-engineer
CI/CD security, SAST/DAST pipelines, supply chain security, container scanning, and security automation specialist. Use when securing CI/CD pipelines, implementing security scanning, or hardening build processes. Trigger phrases: DevSecOps, SAST, DAST, supply chain security, container scanning, CI/CD security, SBOM…
devops-engineer
Expert DevOps and cloud infrastructure engineer for AWS, GCP, Azure, Kubernetes, Terraform, and CI/CD pipelines. Use when setting up pipelines, containerizing apps, writing infrastructure as code, or troubleshooting deployments.