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 obto-inc/platform --skill platformgit clone --depth 1 https://github.com/obto-inc/platformWrote 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/obto-inc/platform/platform)<a href="https://agentmods.dev/skills/obto-inc/platform/platform"><img src="https://agentmods.dev/badge/skills/obto-inc/platform/platform/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/obto-inc/platform/platform"><img src="https://agentmods.dev/badge/skills/obto-inc/platform/platform.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.00241 | $0.01871 |
| Opus 5.5 | $0.00096 | $0.00748 |
| Sonnet 5.5 | $0.00048 | $0.00374 |
| Haiku 4.5 | $0.00024 | $0.00187 |
Grade A, and why
obto-developer scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Reading code:** `search(query, appName, domain)` to find artifacts, `fetch(id)` for whole small ones, `obto_grep_artifact` for line-numbered slices of large ones. **Editing:** `obto_patch_artifact` (line-addressed, w How it starts
The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OBTO Developer Skill
You are an autonomous engineer on the OBTO platform. Every artifact of an application — pages, client and server scripts, routes, stylesheets, policies, UI templates, data sources — is a MongoDB record scoped by (appName, domain); the runtime compiles those records into live pages and APIs. You call the MCP tools yourself — never instruct the user to run commands or invoke tools manually.
Rule 0 — the stateless contract
Call obto_whoami first in every conversation. The server keeps no session-level active app or domain: pass appName AND domain explicitly on every app-scoped call. If the user hasn't named an app, ask, or discover with obto_list_all_apps / obto_find_app_by_name. If whoami returns operatorIdentity: true, never build into the home domain — ask the human which tenant domain to target.
Rule 0.1 — never leave the MCP surface
The MCP tools are the whole platform. Create, deploy, diagnose, verify, and recover entirely through them: never use or recommend kubectl, pod restarts/recycles, container shells, SSH, a DNS console, a cloud console, or direct database access to make an OBTO app work — not even when you happen to have that access. A tenant has only MCP, so a fix that needs more than MCP is a platform defect to report, not a task to complete. When a write says pending_platform_activation, activation is the platform's job: try obto_reload_scripts, otherwise verify with a probe only the new code can answer. When a host serves the wrong thing, run obto_repair_publish (dry_run, then repair). When a tool refuses on capability, believe it and report the code.
Rule 0.5 — the server teaches; read what it serves
obto_whoami returns availableResources: server-served guides (obto://guide/quickstart, obto://guide/blueprints, obto://guide/public-app-baseline, obto://guide/patching, …), each with a whenToRead hint. They are the source of truth for per-collection code shapes — read the ones that match the task before writing code. Tool descriptions and error envelopes are authoritative: failures return {ok:false, error, hint} and the hint names the fix; follow it before improvising. A -32005 refusal means the server shipped a new tool surface — reconnect for a fresh catalog.
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 Changed · +4 lines a5c5753b6e27
- 1mo ago First seen · 49 lines · 241 tokens per session scan A a96ee23a2766
obto-developer is a skill published in the GitHub repository obto-inc/platform (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 241 tokens to every session and 1,871 once invoked, about $0.0010 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
n8n-subworkflows
Build reusable, composable n8n sub-workflows. Use when extracting shared logic, building anything multi-step or reused across workflows, or any workflow over 10 nodes — and whenever the user mentions sub-workflows, Execute Workflow, reuse, shared/common logic, modular workflows, "Define Below" inputs…
n8n-code-tool
Write JavaScript or Python for the n8n Custom Code Tool (@n8n/n8n-nodes-langchain.toolCode) — the AI-agent-callable tool, NOT the workflow Code node. Use when building a Code Tool attached to an AI Agent, writing code that an LLM will invoke, parsing the query input, returning a string result, defining an input schema…
sanity-singletons
Configure singleton documents in a Sanity Studio using the document.singletons registry. Use when a developer wants a fixed-id document (settings, navigation, footer) edited in place, hidden from the default content list, with no "create new" or "duplicate" affordances — or when migrating a userland singleton…
sanity-best-practices
Sanity development best practices for schema design, GROQ queries, TypeGen, Visual Editing, images, Portable Text, Studio structure, localization, migrations, Sanity Functions, webhooks, Blueprints, and framework integrations such as Next.js, Nuxt, Astro, Remix, SvelteKit, Angular, Hydrogen, the App SDK, and Studios…
tech-specs
To define clear, testable tech specs from requirements — target-state architecture, contracts, interfaces.
api-forge
Design REST/GraphQL APIs with OpenAPI 3.1, error handling, pagination, rate limiting, webhooks, and idempotency. Use when user asks to design an API, create endpoints, define REST/GraphQL schema, or generate OpenAPI spec. Do NOT use for database schema design, frontend API integration, or non-HTTP protocols (gRPC…