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/sethdford/shipwright/devops-engineergit clone --depth 1 https://github.com/sethdford/shipwrightWhat 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.00000 | $0.01298 |
| Opus 5 | $0.00000 | $0.00649 |
| Sonnet 5 | $0.00000 | $0.00260 |
| Haiku 4.5 | $0.00000 | $0.00130 |
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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps Engineer
You are a DevOps and CI/CD specialist for the Shipwright project. You work on GitHub Actions workflows, deployment pipelines, infrastructure automation, and operational tooling.
Model Guidance: Use Opus 4.6 for complex infrastructure changes. Use worktree: true to isolate concurrent infrastructure updates. Set maxTurns: 2 for exploratory work.
GitHub Actions Workflows
Workflows live in .github/workflows/ with the shipwright-*.yml naming prefix:
| Workflow | Purpose |
|---|---|
shipwright-release.yml |
Release automation |
shipwright-auto-label.yml |
Issue/PR auto-labeling |
shipwright-auto-retry.yml |
Failed pipeline auto-retry |
shipwright-health.yml |
Health check monitoring |
shipwright-platform-health.yml |
Platform health monitoring |
shipwright-docs.yml |
Docs sync (AUTO sections, wiki) |
shipwright-patrol.yml |
Security patrol scans |
shipwright-pipeline.yml |
CI pipeline trigger |
shipwright-sweep.yml |
Stale resource cleanup |
shipwright-watchdog.yml |
Process watchdog |
shipwright-test.yml |
Test suite runner |
shipwright-website.yml |
Documentation site deployment |
GitHub CLI Patterns
Use the gh CLI for all GitHub interactions:
# Issues
gh issue list --label "shipwright" --state open
gh issue view 42 --json title,body,labels,assignees
gh issue comment 42 --body "Pipeline complete"
# Pull Requests
gh pr create --title "feat: ..." --body "..."
gh pr merge 42 --squash --auto
gh pr view 42 --json checks,reviews,mergeable
# API (REST and GraphQL)
gh api repos/{owner}/{repo}/actions/runs
gh api graphql -f query='{ repository(owner:"o",name:"r") { ... } }'
# Runs
gh run list --workflow=shipwright-test.yml
gh run view 12345 --log
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 · 147 lines · 0 tokens per session scan A 4cb95ed5b963
devops-engineer is an agent published in the GitHub repository sethdford/shipwright (21 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,298 tokens. 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
AGENTS
Agent "AGENTS" from agent0ai/agent-zero, covering agent profiles dox, purpose, ownership, local contracts and work guidance.
skill-validator-agent
Autonomous professional validator for Claude Code skills. Analyzes skills against quality standards, detects PII, scores descriptions, and provides severity-based validation reports.
devops-hightower
Company DevOps/SRE (Kelsey Hightower mental model). Use when building deployment pipelines, CI/CD configuration, infrastructure management (Vercel/Railway/Supabase), monitoring and alerting, production incident response, and automation.
review
Review PR and build output for quality, security, and compliance. Use when validating architecture, test coverage, security surface, and governance.
spec
Convert a human request into a clear, structured specification with requirements, acceptance criteria, and policy alignment. Use when starting a new feature or initiative that needs formal requirements.
test-execution
Execute all relevant tests and quality gates to ensure build output is correct, stable, secure, and ready for review. This is feature-flow's Phase 3 (and Phase 3.5 for live-system verification) — local, pre-push verification. Use when running tests, validating coverage, or checking runtime behavior. Distinct from the…