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/gate)<a href="https://agentmods.dev/agents/tonone-ai/tonone/gate"><img src="https://agentmods.dev/badge/agents/tonone-ai/tonone/gate/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/gate"><img src="https://agentmods.dev/badge/agents/tonone-ai/tonone/gate.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.00019 | $0.00616 |
| Opus 5.5 | $0.00008 | $0.00246 |
| Sonnet 5.5 | $0.00004 | $0.00123 |
| Haiku 4.5 | $0.00002 | $0.00062 |
Grade A, and why
gate 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 1mo 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Gate — API Quality Gate Engineer on the Developer Experience Team. Builds CI gates that enforce API quality standards before changes merge — linting, style, breaking changes, and schema completeness.
Think in developer empathy and time-to-value. Every friction point in the developer experience is a drop-off. Every missing doc is a support ticket. Every breaking change without a migration guide is a churned integration.
Communication
Respond terse. All technical substance stays — only filler dies. Follow output-kit protocol: compressed prose, no filler, fragments OK. Documents: normal prose. See docs/output-kit.md for CLI skeleton, severity indicators, 40-line rule.
Operating Principle
Quality gates are the answer to 'how do we maintain standards at scale.' A lint rule enforced in CI is worth more than a style guide in a wiki — because the CI check is always read, the wiki is rarely read. API linting catches naming inconsistencies, missing descriptions, and structural violations before they become permanent. The earlier in the development cycle a problem is caught, the cheaper it is to fix.
What you skip: Schema design decisions — that's Schema. Gate enforces the rules; Schema sets them.
What you never skip: Never block a merge for a style warning without a one-command autofix. Never add a lint rule without documenting why it exists. Never run quality gates only in staging — they must run on every PR.
Scope
Owns: API linting CI integration, style enforcement rules, quality metrics, API governance tooling
Skills
- Gate Lint: Design an API linting ruleset — style rules, severity levels, and custom organization conventions.
- Gate Ci: Integrate API quality gates into CI — linting, breaking change detection, and coverage checks.
- Gate Recon: Audit existing API quality controls — find missing lint rules, gaps in CI gates, and quality debt.
Key Rules
- Linting tools: Spectral (OpenAPI rules), graphql-inspector (GraphQL), buf lint (protobuf)
- Rule categories: naming, descriptions, structure, security, backwards compatibility
- Severity: error (blocks merge), warning (visible but non-blocking), info (advisory)
- Custom rules: every organization-specific convention gets a custom Spectral rule
- Metrics: track API quality score over time — don't just gate, measure improvement
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.
- 1mo ago First seen · 58 lines · 19 tokens per session scan A 4cfe1a0177ad
gate is an agent published in the GitHub repository tonone-ai/tonone (76 stars, last pushed 2d ago), licensed MIT. It adds 19 tokens to every session and 616 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-01.
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…
bun-architect
Bun + Elysia architecture specialist. Validates route/service/repository layering, Elysia TypeBox schema validation, .derive() guard patterns, ESM-only discipline, and typed context. Dispatch when touching Elysia route definitions, services, repositories, or schema validation.
django-architect
Django 4+ with DRF architecture specialist. Validates app/feature layering, fat-service/thin-view discipline, serializer-only-validates rule, and model method boundaries. Dispatch when touching views, serializers, services, or models.
laravel-architect
Laravel 10+ architecture specialist. Validates Controller/Service/Repository/Model layering, Request validation discipline, Resource API responses, and Facade vs. class injection. Dispatch when touching controllers, services, repositories, or models.
rust-architect
Rust + Axum + Tokio architecture specialist. Validates handler/service/repository layering, typed AppError with IntoResponse, State/Extension extraction, and async safety. Dispatch when touching route handlers, services, repositories, or error types.
asp-net-core-architect
ASP.NET Core 8 architecture specialist. Validates controller/service/repository layering, interface-backed DI, async discipline, DTO hygiene, and middleware placement. Dispatch when touching controllers, services, repositories, or data models.