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 nikships/droidproxy --skill droid-model-setupgit clone --depth 1 https://github.com/nikships/droidproxyWrote 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/nikships/droidproxy/droid-model-setup)<a href="https://agentmods.dev/skills/nikships/droidproxy/droid-model-setup"><img src="https://agentmods.dev/badge/skills/nikships/droidproxy/droid-model-setup/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/nikships/droidproxy/droid-model-setup"><img src="https://agentmods.dev/badge/skills/nikships/droidproxy/droid-model-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 5 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00166 | $0.02055 |
| Opus 5.5 | $0.00066 | $0.00822 |
| Sonnet 5.5 | $0.00033 | $0.00411 |
| Haiku 4.5 | $0.00017 | $0.00205 |
Grade A, and why
droid-model-setup 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Droid model setup
Turns any OpenAI-compatible (and most Anthropic-compatible) endpoint into a first-class Droid
model. Covers spec lookup, safe writes to ~/.factory/settings.json, session-default effort
wiring, and empirical verification. Knowledge below was verified Aug 2026 against the real binary
by capturing Droid's outgoing request bodies.
Workflow for "set X, Y, Z models up for a Droid"
- Resolve specs per model (ask only what cannot be looked up; be agentic otherwise).
- OpenRouter-hosted model: fetch
https://openrouter.ai/<vendor>/<slug>— gives context window, max completion tokens, supported reasoning efforts, pricing. - Other providers: check their docs/API reference for context length and output cap.
- Note whether thinking/reasoning can be toggled and via which parameter.
- OpenRouter-hosted model: fetch
- Determine endpoint + credentials.
- Same provider already registered in settings? Reuse its key with the script's
--reuse-key-from <existing-model-id>(reads the real stored bytes; the asterisks you see in file reads are display-only redaction, and Python sees through them). - New provider: ask the user for the base URL and API key if genuinely unknown. Defaults:
OpenRouter
https://openrouter.ai/api/v1, LM Studiohttp://127.0.0.1:1234/v1, llama.cpp/vLLM/Ollama-OpenAIhttp://127.0.0.1:<port>/v1. - Provider field:
generic-chat-completion-apicovers every OpenAI-compatible endpoint tested (OpenRouter, W&B, LM Studio, MTPLX).openaialso works for OpenAI-compat APIs.
- Same provider already registered in settings? Reuse its key with the script's
- Write entries with the helper script (never hand-edit settings.json — see gotchas).
Model
idin settings becomes the CLI-facing name:-m custom:<id>. - Set session defaults if the user wants one of them as the daily driver
(
set-defaultssubcommand sets model + matching reasoningEffort together). - Verify live, then report exactly what was configured and proven.
Hard rules
Never text-edit ~/.factory/settings.json. Existing apiKey values render as runs of
asterisks inside the agent's file viewer; a string-replacement edit that touches those lines
writes literal asterisks to disk and destroys real keys. Use scripts/droid_models.py, which
mutates parsed JSON (untouched values stay byte-identical), backs the file up first, and
afterward diffs every pre-existing key — restoring automatically and failing loudly if anything
changed. If you must edit manually anyway (new top-level keys etc.), anchor edits far away from
apiKey lines, then diff {id: len(apiKey)} old-vs-new via Python before declaring success.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 143 lines · 166 tokens per session scan A 14e22be7f35f
droid-model-setup is a skill published in the GitHub repository nikships/droidproxy (124 stars, last pushed yesterday), licensed MIT. It adds 166 tokens to every session and 2,055 once invoked, about $0.0007 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-08-30.
Other skills, from other repositories
contacts
Manage contacts, communication channels, access control, and invite links.
gmail
Manage Gmail email — drafting, sending, organizing, filters, vacation replies, and inbox analysis.
app-builder
Build and edit small, personal visual tools and artifacts — dashboards, trackers, calculators, data visualizations, charts, simple landing pages, and slide decks the user wants for THEMSELVES. This is the right skill whenever the user asks to "visualize this," "make a chart," or "build an artifact" for their own use…
assistant-migration
Migrate from ChatGPT, Claude, OpenClaw, Hermes, Manus, and other AI assistants into Vellum by inspecting their data exports, conversation archives, files, prompts, custom instructions, memory, saved memories, tools, GPTs, workflows, integrations, and relationships, then mapping as much as safely possible into Vellum…
guardian-verify-setup
Set up channel verification for phone, Telegram, Slack, Discord, or email channels via outbound verification flow.
stripe-link-wallet
Agent wallet on the Stripe Link CLI (link-cli). Connect the wallet, then buy, purchase and pay for things on the user's behalf via approved spend requests, one-time-use cards, and 402 / Machine Payment Protocol (MPP) payments.