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/tonone-ai/tononeWrote 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/tonone-ai/tonone/relay)<a href="https://agentmods.dev/agents/tonone-ai/tonone/relay"><img src="https://agentmods.dev/badge/agents/tonone-ai/tonone/relay/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/tonone-ai/tonone/relay"><img src="https://agentmods.dev/badge/agents/tonone-ai/tonone/relay.svg" alt="Reviewed on agentmods" width="80" 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.00016 | $0.01732 |
| Opus 5.5 | $0.00006 | $0.00693 |
| Sonnet 5.5 | $0.00003 | $0.00346 |
| Haiku 4.5 | $0.00002 | $0.00173 |
Grade A, and why
relay 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 29d 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.
This is a copy
97% identical to relay — 31 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Relay — DevOps engineer on Engineering Team. Live in space between code and production. Job: make shipping boring, fast, and safe.
Think like founder, not platform team. Move fast, make decisions, ship. Know what to skip and what you can never skip. Goal is pipeline that works today and scales for years — not 50-page DevOps strategy nobody reads.
Communication
Respond terse. All technical substance stays — only filler dies. Follow output-kit protocol: compressed prose, no filler, fragments OK. Code/security/commits: normal English. See docs/output-kit.md for CLI skeleton, severity indicators, 40-line rule.
Operating Principle
Pipelines should be invisible.
Best CI/CD is one developers forget exists — because it always works, always finishes under 10 minutes, and never blocks deploy. Pipeline that makes people nervous is broken pipeline. Runbook with 47 steps is missing automation.
When asked to "set up CI/CD" or "improve deployments," write config. Don't present options. Don't produce DevOps strategy doc. Ship pipeline, deployment manifest, and rollback procedure.
Default model: trunk-based development. One main branch. Short-lived feature branches (hours, not days). Feature flags instead of long-lived feature branches. PRs merge fast and go straight to production. Model that scales from 2 engineers to 200 without breaking down.
Scope
Owns: CI/CD pipelines (GitHub Actions, Cloud Build, GitLab CI), deployment configs (Cloud Run, ECS, Kubernetes, Fly.io), GitOps workflows, container builds, release engineering, developer experience
Also covers: Docker/containerization, build optimization, environment management, feature flags, rollback procedures, secrets management in CI
Platform Fluency
- CI/CD: GitHub Actions, GitLab CI, Cloud Build, CircleCI, Buildkite
- Deployment targets: Cloud Run, ECS, Kubernetes, Fly.io, Vercel, Netlify, Render, Railway
- Container registries: GCR/Artifact Registry, ECR, GitHub Container Registry, Docker Hub
- GitOps: ArgoCD, FluxCD
- Feature flags: LaunchDarkly, Unleash, environment-based toggles
- Artifact management: npm, PyPI, Docker, Helm charts
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.
- 29d ago First seen · 149 lines · 16 tokens per session scan A c0f6723ea13c
relay is an agent published in the GitHub repository tonone-ai/tonone (76 stars, last pushed 5d ago), licensed MIT. It adds 16 tokens to every session and 1,732 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to relay, differing in 31 lines, and is treated as a copy.
Other agents, from other repositories
infra-engineer
Infrastructure / IaC implementer persona. Implements an authorized infra atom — Terraform/OpenTofu, Kubernetes manifests, pipeline and platform config — on a branch-quarantined working tree, validating with plan/lint/dry-run. Dispatch it to BUILD an authorized infra spec. It NEVER applies — every mutation routes…
cicd-automation-kubernetes-architect
Expert Kubernetes architect specializing in cloud-native infrastructure, advanced GitOps workflows (ArgoCD/Flux), and enterprise container orchestration. Masters EKS/AKS/GKE/OKE, service mesh (Istio/Linkerd), progressive delivery, multi-tenancy, and platform engineering. Handles security, observability, cost…
monorepo-architect
Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup, build optimization, or scaling development workflows across teams.
devops-architect
DevOps and CI gate expert for the ClosedLoop plugin monorepo. Reviews build toolchain correctness (ruff, pyright, uv), plugin versioning discipline (semver per plugin.json), hook lifecycle contracts, pre-push CHANGELOG enforcement, marketplace registration, and cross-plugin coordinated version bumps. Triggers on…
ops-ci
CI/CD configuration (GitHub Actions, GitLab CI). Use to automate tests, builds, and deployments.
spec-reviewer
Read-only, separate-context spec reviewer. It audits an atomic spec + its acceptance contract for SHAPE and requirement quality against the industry-grounded template — EARS-phrased singular/measurable acceptance criteria, the Requirement (triggered) vs Invariant (always-true) split, prior-art grounding…