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 davidmosiah/ninenine-mcp --skill skillgit clone --depth 1 https://github.com/davidmosiah/ninenine-mcpWrote 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/davidmosiah/ninenine-mcp/skill)<a href="https://agentmods.dev/skills/davidmosiah/ninenine-mcp/skill"><img src="https://agentmods.dev/badge/skills/davidmosiah/ninenine-mcp/skill/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/davidmosiah/ninenine-mcp/skill"><img src="https://agentmods.dev/badge/skills/davidmosiah/ninenine-mcp/skill.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.00093 | $0.00642 |
| Opus 5 | $0.00046 | $0.00321 |
| Sonnet 5 | $0.00019 | $0.00128 |
| Haiku 4.5 | $0.00009 | $0.00064 |
Grade A, and why
ninenine 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 4d 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.
What it actually says
99 — skill or MCP
Unofficial. Not 99Food, 99Pay, 99Entrega, or corp B2B.
Same binary either way. Mutation gates live in the server, not in this file.
Choose a surface
MCP — tools appear natively after stdio/HTTP config:
{ "mcpServers": { "ninenine": { "command": "npx", "args": ["-y", "ninenine-mcp-unofficial"] } } }
Do not put mutation flags in that snippet.
Skill / CLI — no MCP client required. Same tools:
npx -y ninenine-mcp-unofficial doctor --json
npx -y ninenine-mcp-unofficial call ninenine_capabilities --json '{}'
npx -y ninenine-mcp-unofficial call ninenine_estimate --json '{"from_lat":-3.73,"from_lng":-38.52,"to_lat":-3.74,"to_lng":-38.54}'
If MCP tools named ninenine_* are already available, use them. Do not also shell out.
Setup (once)
npx -y ninenine-mcp-unofficial setup
npx -y ninenine-mcp-unofficial auth --from-header "Bearer …"
Token is a captured passenger Authorization to api.99taxis.mobi, stored at ~/.ninenine-mcp/tokens.json (0600). Estimates work without a token; request-ride stays blocked.
Loop
ninenine_connection_status(ordoctor --json). Expectunofficialandnever_pays_by_default.ninenine_estimatewith origin/destination. Always show 99Pop and 99Moto with price/ETA. Optionalninenine_multi_estimate. Never request a car.- History / track only if asked. GPS, street, phone stay redacted.
- Stop. Do not call
ninenine_request_rideorninenine_cancel_rideunless the user clearly asked to request/cancel this ride. If the tool returnsUSER_ACTION_REQUIRED, report that and stop. Do not invent env flags.
Never
- Enable mutations from this skill
- Paste tokens into git, chat logs, or the prompt
- Treat guest as able to pay
- Open 99Food
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.
- 4d ago Changed 2e6b6b99e8d7
- 8d ago First seen · 59 lines · 93 tokens per session scan A 56ec8232abb3
ninenine is a skill published in the GitHub repository davidmosiah/ninenine-mcp (1 stars, last pushed 7d ago), licensed MIT. It adds 93 tokens to every session and 642 once invoked, about $0.0005 per session on Opus 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…