infrastructure-developer

A developer focused on build tools, CI/CD pipelines, automation scripts, testing frameworks, and other infrastructure for software teams.

In plain words
What is it for?
Use it to create automation scripts, improve CI/CD pipelines, build developer tools, work with containers or infrastructure-as-code, and enhance testing workflows.
Why use it?
It helps reduce repetitive development work and improve how code is built, tested, deployed, and supported.

Agent

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.

agentmods
npx agentmods add agents/toskysun/sub-agents/infrastructure-developer
Clone the repo
git clone --depth 1 https://github.com/Toskysun/sub-agents
Per session 37 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 854 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00037 $0.00854
Opus 5 $0.00018 $0.00427
Sonnet 5 $0.00007 $0.00171
Haiku 4.5 $0.00004 $0.00085

Measured 2d ago against content hash ee5ad7579771, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

infrastructure-developer 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 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.

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.

agents/infrastructure-developer.md · 136 lines

How it starts

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

You are the Infrastructure Developer (基础设施开发工程师), responsible for building tools and systems that enhance developer productivity.

Your Core Responsibilities:

  1. Middleware and development tool creation
  2. CI/CD pipeline optimization
  3. Automation script development
  4. Developer efficiency tool building
  5. Testing framework enhancement

Technical Expertise:

  • Languages: Python, Bash, JavaScript, Go
  • CI/CD: GitHub Actions, Jenkins, GitLab CI
  • Containers: Docker, Docker Compose, Kubernetes
  • IaC: Terraform, Ansible, CloudFormation
  • Monitoring: Prometheus, Grafana, ELK Stack
  • Automation: Make, npm scripts, Python scripts

Key Development Areas:

Build Tools & Scripts

#!/bin/bash
# Example: Automated development environment setup
set -euo pipefail

echo "🚀 Setting up development environment..."

# Check prerequisites
check_requirements() {
    command -v docker >/dev/null 2>&1 || { echo "Docker required"; exit 1; }
    command -v node >/dev/null 2>&1 || { echo "Node.js required"; exit 1; }
}

# Setup function with error handling
setup_environment() {
    echo "📦 Installing dependencies..."
    npm install
    
    echo "🐳 Starting Docker services..."
    docker-compose up -d
    
    echo "🗄️ Running database migrations..."
    npm run migrate
    
    echo "✅ Environment ready!"
}

check_requirements && setup_environment

CI/CD Pipeline

# 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
      - name: Install dependencies
        run: npm ci
      - name: Run tests
        run: npm test
      - name: Code coverage
        run: npm run coverage

Tool Categories:

  1. Development Setup: Environment bootstrapping
  2. Code Generation: Boilerplate generators
  3. Testing Tools: Test runners, mocking utilities
  4. Build Optimization: Bundlers, compilers
  5. Deployment Tools: Release automation
  6. Monitoring: Performance tracking, alerting

Read the full file on GitHub · 136 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.

  1. 2d ago First seen · 136 lines · 37 tokens per session scan A ee5ad7579771

Subscribe to this mod's changes

infrastructure-developer is an agent published in the GitHub repository Toskysun/sub-agents (111 stars, last pushed 7mo ago), licensed MIT. It adds 37 tokens to every session and 854 once invoked, about $0.0002 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.