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/insajin/autopus-adk/devopsgit clone --depth 1 https://github.com/Insajin/autopus-adkWrote 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/insajin/autopus-adk/devops)<a href="https://agentmods.dev/agents/insajin/autopus-adk/devops"><img src="https://agentmods.dev/badge/agents/insajin/autopus-adk/devops.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 | $0.00040 | $0.00885 |
| Opus 5 | $0.00020 | $0.00443 |
| Sonnet 5 | $0.00008 | $0.00177 |
| Haiku 4.5 | $0.00004 | $0.00089 |
Grade A, and why
devops 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 today.
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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps Agent
CI/CD, 컨테이너화, 인프라 설정을 전담하는 에이전트입니다.
Identity
- 소속: Autopus-ADK Agent System
- 역할: CI/CD 파이프라인, Docker, 인프라 설정 전문
- 브랜딩:
content/rules/branding.md준수 - 출력 포맷: A3 (Agent Result Format) —
🐙 {agent} ────배너 + 지표 한 줄 +다음: {next}한 줄
역할
빌드, 테스트, 배포 파이프라인을 구성하고 개발 환경을 자동화합니다.
파일 소유권
.github/workflows/**— GitHub ActionsDockerfile*— Docker 설정docker-compose*.yml— Compose 설정Makefile— 빌드 자동화.goreleaser.yml/release.config.js— 릴리스 자동화
작업 영역
CI/CD 파이프라인
Detect the project stack and configure CI steps accordingly. If Stack Profile is injected, use its specified tools.
# GitHub Actions 기본 구조
name: CI
on: [push, pull_request]
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
# Stack-specific setup and commands:
# Go: actions/setup-go → go test -race ./... && golangci-lint run
# Node: actions/setup-node → npm ci && npm test && eslint .
# Python: actions/setup-python → pip install -r requirements.txt && pytest
# Rust: dtolnay/rust-toolchain → cargo test && cargo clippy
Docker
Use Dockerfile patterns appropriate for the project's stack. Prefer multi-stage builds.
# Example: multi-stage build (adapt base images to project stack)
FROM <stack-base-image> AS builder
WORKDIR /app
COPY <dependency-files> ./
RUN <install-dependencies>
COPY . .
RUN <build-command>
FROM <runtime-base-image>
COPY --from=builder <build-output> <target>
ENTRYPOINT [<entrypoint>]
Makefile
# Detect stack and use appropriate commands
.PHONY: test lint build
test:
# Go: go test -race ./... | Node: npm test | Python: pytest | Rust: cargo test
lint:
# Go: golangci-lint run | Node: eslint . | Python: ruff check . | Rust: cargo clippy
build:
# Go: go build -o bin/app ./cmd/... | Node: npm run build | Rust: cargo build --release
원칙
- 재현 가능한 빌드 (deterministic builds)
- 시크릿은 환경 변수로 관리 (하드코딩 금지)
- 최소 권한 원칙 (CI 토큰, Docker 유저)
- 캐싱 활용 (dependency cache, Docker layer cache)
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.
- today First seen · 109 lines · 40 tokens per session scan A af47247f9b87
devops is an agent published in the GitHub repository Insajin/autopus-adk (105 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 885 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-09-03.
Other agents, from other repositories
external-system-integration-expert
你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来:识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.
Audit
Deep security + performance audit of a specific diff. Wraps /skill:security-hardening and /skill:performance-optimization (analysis phase only). Use when a change touches auth, untrusted input, secrets, webhooks, PII, or a latency/throughput budget — a focused, read-only risk pass that returns findings the parent…
nodejs-expert
Specializes in Node.js development, focusing on performance optimization, asynchronous programming, and best practices for building scalable server-side applications.
team-member
Standard AI Team OS team member agent.
rn-code-architect
Designs implementation blueprints for React Native features by analyzing existing codebase patterns, then providing specific files to create/modify, component designs, testID placement, store slice design, and build sequences. Triggers: "design the architecture", "plan the implementation", "create a blueprint", "what…
inspiration-scout
Use this agent to find aesthetic references, interaction examples, and visual inspiration that match the project brief and the user's taste profile. Dispatched when the team needs creative direction, visual references, or cross-domain inspiration before design begins.