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 skills add tonone-ai/tonone --skill relay-pipelinegit 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/skills/tonone-ai/tonone/relay-pipeline)<a href="https://agentmods.dev/skills/tonone-ai/tonone/relay-pipeline"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/relay-pipeline/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/skills/tonone-ai/tonone/relay-pipeline"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/relay-pipeline.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.00034 | $0.02554 |
| Opus 5.5 | $0.00014 | $0.01022 |
| Sonnet 5.5 | $0.00007 | $0.00511 |
| Haiku 4.5 | $0.00003 | $0.00255 |
Grade A, and why
relay-pipeline 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 17d 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.
How it starts
The opening of the file, as written. The whole thing — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build CI/CD Pipeline
You are Relay — the DevOps engineer from the Engineering Team.
You write the pipeline. You don't present options. Given the project's stack and deployment target, you produce the actual CI config file ready to commit.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Step 0: Read the Project
ls -a
cat package.json 2>/dev/null || cat pyproject.toml 2>/dev/null || cat go.mod 2>/dev/null || cat Cargo.toml 2>/dev/null || cat pom.xml 2>/dev/null || true
ls .github/workflows/ 2>/dev/null || true
ls -a | grep -E "(fly\.toml|render\.yaml|vercel\.json|netlify\.toml|app\.yaml|Dockerfile|docker-compose)" 2>/dev/null || true
Determine:
- Language and package manager — Node/npm/pnpm/yarn, Python/uv/pip, Go, Rust/cargo, Java/maven/gradle
- Framework — Next.js, FastAPI, Express, Django, Echo, Axum, Spring Boot
- Runtime version — check
.node-version,.python-version,.tool-versions,Dockerfile - Deployment target — Cloud Run, Fly.io, ECS, Vercel, Render, Railway, Kubernetes, Netlify
- Existing CI — GitHub Actions, GitLab CI, Cloud Build, CircleCI, none
If no CI config exists, default to GitHub Actions.
Step 1: Determine What to Run
Make these decisions now — don't ask:
| What exists | What to run in CI |
|---|---|
eslint/ruff/golangci-lint/clippy in project |
Run it |
| No linter configured | Skip lint stage |
| Test files exist | Run tests with coverage |
| No tests | Run build only; add a comment to add tests |
next build/go build/cargo build/mvn package |
Run build stage |
| Interpreted language, no compile step | Skip build stage |
| Dockerfile or platform deploy file | Add deploy stage |
| No deploy config | Output pipeline without deploy; note what to add |
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.
- 17d ago First seen · 268 lines · 34 tokens per session scan A 6d28b090468a
relay-pipeline is a skill published in the GitHub repository tonone-ai/tonone (76 stars, last pushed 9d ago), licensed MIT. It adds 34 tokens to every session and 2,554 once invoked, about $0.0001 per session on Opus 5.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-27.
Other skills, from other repositories
verify
The profile-parameterized static-validation + test executor (/foundry:verify, SDLC steps 7 & 8). Resolves the ACTIVE stack profile from .foundry/stack-profile.lock (via the merged stack-profile loader's resolvelock) and dispatches the profile-declared staticvalidation (format/lint/typecheck/build) + testrecipe…
cicd-gitops-pipeline
Skill "cicd-gitops-pipeline" from lukasrepublic/agentic-foundry, covering when to trigger, the pipeline shape (six parts, one contract), both build origins, one downstream contract and anti-patterns.
deployment-pipeline-design
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use this skill when designing zero-downtime deployment pipelines, implementing canary rollout strategies, setting up multi-environment promotion workflows, or debugging failed deployment gates in CI/CD.
gitlab-ci-patterns
Build GitLab CI/CD pipelines with multi-stage workflows, caching, and distributed runners for scalable automation. Use when implementing GitLab CI/CD, optimizing pipeline performance, or setting up automated testing and deployment.
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.