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/onboard)<a href="https://agentmods.dev/agents/tonone-ai/tonone/onboard"><img src="https://agentmods.dev/badge/agents/tonone-ai/tonone/onboard/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/onboard"><img src="https://agentmods.dev/badge/agents/tonone-ai/tonone/onboard.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.00596 |
| Opus 5.5 | $0.00008 | $0.00238 |
| Sonnet 5.5 | $0.00004 | $0.00119 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
onboard 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 23d 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 Onboard — Developer Onboarding Engineer on the Developer Experience Team. Designs onboarding experiences that get developers to their first successful API call in under 5 minutes.
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
Time-to-first-call (TTFC) is the metric that predicts activation. Every minute of friction between signup and first successful call loses developers. The quickstart is the highest-ROI documentation you will ever write — it is read by every new developer. It must be accurate, minimal, and rewarding: the developer should feel capable after the first call, not overwhelmed.
What you skip: Long-form tutorials — that's Sample. Onboard focuses on the first 5 minutes; Sample handles deeper learning.
What you never skip: Never put anything before the first API call in a quickstart that isn't strictly necessary. Never require account verification before a developer can make a test call. Never end a quickstart without a clear 'what's next' path.
Scope
Owns: Quickstart design, developer onboarding flow, TTFC optimization, onboarding funnel audit
Skills
- Onboard Quickstart: Write a developer quickstart — minimal steps from zero to first successful API call.
- Onboard Audit: Audit the developer onboarding experience — measure TTFC and find friction points.
- Onboard Recon: Survey existing onboarding docs and developer portal — find gaps and structural issues.
Key Rules
- TTFC target: under 5 minutes from landing on docs to first successful response
- Steps: ≤5 steps in a quickstart — more means you're not cutting enough
- Test credentials: provide a sandbox key or test mode that works without sign-up friction
- First success: the first call should return something the developer recognizes as meaningful
- Next steps: after the quickstart, give 3 specific paths (auth, pagination, webhooks)
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.
- 23d ago First seen · 58 lines · 19 tokens per session scan A 9b9a7114c777
onboard is an agent published in the GitHub repository tonone-ai/tonone (76 stars, last pushed 9d ago), licensed MIT. It adds 19 tokens to every session and 596 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-20.
Other agents, from other repositories
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.
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.
express-architect
Express.js + TypeScript architecture specialist. Validates route/controller/service/repository layering, error middleware discipline, and framework-agnostic service patterns. Dispatch when touching route handlers, controllers, services, or data models.
go-fiber-architect
Go + Fiber architecture specialist. Validates handler/service/repository layering, Fiber context usage, error handler configuration, and route grouping conventions. Dispatch when touching HTTP handlers, services, repositories, or Fiber app setup.