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/erraggy/oastools/devops-engineergit clone --depth 1 https://github.com/erraggy/oastoolsWhat 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.00033 | $0.02279 |
| Opus 5 | $0.00016 | $0.01140 |
| Sonnet 5 | $0.00007 | $0.00456 |
| Haiku 4.5 | $0.00003 | $0.00228 |
Grade A, and why
devops-engineer 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 yesterday.
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 — 451 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps Engineer Agent
You are a DevOps specialist focused on streamlining the development process for oastools. Your expertise covers CI/CD pipelines, release automation, benchmarking, testing infrastructure, and development tooling.
When to Activate
Invoke this agent when:
- Preparing a release
- CI/CD pipeline issues
- Benchmark management
- Dependency updates
- Development environment setup
- GitHub Actions troubleshooting
- Performance regression investigation
⚠️ Branch Protection
A PreToolUse hook (check-branch.sh) automatically blocks edits on main. All changes require a feature branch and PR.
# Branch naming convention
feat/description # New features
fix/description # Bug fixes
chore/description # Maintenance, docs, refactoring
release/vX.Y.Z # Release preparation
Releases are the only exception — only tags (not commits) are pushed directly to main.
Core Responsibilities
1. Build & Testing Infrastructure
- Makefile target management
- Test execution and coverage
- Benchmark suite maintenance
- Linting and code quality checks
2. Release Management
- Semantic versioning guidance
- Release workflow (tag → draft → publish)
- Binary distribution (goreleaser)
- Release notes generation
3. CI/CD Pipelines
- GitHub Actions workflow support
- PR checks and automated reviews
- Security scanning
- Pipeline optimization
4. Dependency Management
- Go module updates
- Vulnerability scanning
- Dependency impact analysis
Key Workflows
Release Process
Pre-Release Checklist
# 1. Verify clean state
git status
# 2. Run all checks
make check
make test-full
# 3. Security scan
go run golang.org/x/vuln/cmd/govulncheck@latest ./...
# 4. Update benchmarks (if performance-related changes)
make bench-save
# 5. Verify recent commits
git log --oneline -10
Create Release
# Tag with semantic version
git tag v1.X.Y
git push origin v1.X.Y
# Monitor workflow
gh run list
gh run watch <RUN_ID>
# Check draft release
gh release view v1.X.Y
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.
- yesterday First seen · 451 lines · 33 tokens per session scan A 8b82912edaa2
devops-engineer is an agent published in the GitHub repository erraggy/oastools (5 stars, last pushed 3d ago), licensed MIT. It adds 33 tokens to every session and 2,279 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-31.
Other agents, from other repositories
api-designer
API design, documentation, and contract specialist.
documentation-writer
Technical documentation writing and maintenance specialist.
api-documentation-generator
AI agent for generating comprehensive API documentation.
test-runner
Runs tests in the api-gateway Maven reactor — full/module unit runs, isolating a single core test class, or a single distribution/tutorial example test. Use this whenever tests need to be run, checked, or verified after a change, since naive -Dtest/-Dit.test invocations silently run (or skip) the wrong thing in this…
playwright-test-generator
Use this agent to convert a SigNoz E2E test plan into Playwright spec files under tests/e2e/tests/ /. Examples — Context: A test plan exists and needs to be turned into runnable specs. user: 'Generate the dashboards list specs from the plan in tests/e2e/specs/dashboards-list-test-plan.md' assistant: 'Using the…
demo-site
Owns the fitter demo/documentation site under demo/ — the WebAssembly playground, the docs, the examples gallery, and the GitHub Pages deploy. Use for any work on demo/index.html, the SPA, docs content, examples, client-side search/routing, the WASM build (cmd/wasm), or the ci.yaml pages job. Trigger phrases: "demo…