Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/contains-studio/fable-delegatornpx agentmods add skills/contains-studio/fable-delegator/use-cliproxyWrote 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/contains-studio/fable-delegator/use-cliproxy)<a href="https://agentmods.dev/skills/contains-studio/fable-delegator/use-cliproxy"><img src="https://agentmods.dev/badge/skills/contains-studio/fable-delegator/use-cliproxy.svg" alt="Measured on agentmods" 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.00103 | $0.01434 |
| Opus 5 | $0.00051 | $0.00717 |
| Sonnet 5 | $0.00021 | $0.00287 |
| Haiku 4.5 | $0.00010 | $0.00143 |
Grade A, and why
use-cliproxy 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 7d 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.
Verify: `curl -s -H "Authorization: Bearer $KEY" http://127.0.0.1:8317/v1/models` → 200 with a model list (401 without the key confirms auth is enforced). How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLIProxyAPI Subagent Skill
CLIProxyAPI (cliproxy) is a local server that reuses your CLI subscription OAuth logins (Codex, Claude, Gemini, Grok, Antigravity, Kimi) and re-exposes them as OpenAI- and Anthropic-compatible HTTP endpoints. It strips the agent harness — so a call sends only your prompt, none of the 15–23k tokens of system-prompt + tool-definition boilerplate an agent CLI prepends per invocation.
When to use this vs. the agent CLIs — THE decision rule
| Task shape | Use | Why |
|---|---|---|
| Agentic / implementation — edit files, run bash, hold repo context, multi-step build, "go implement X" | agent CLI (use-codex / use-grok / use-cursor / use-agy / use-droid) |
The harness (file/bash/tool loop) is the entire value. A raw endpoint can only return text. |
| Bulk raw generation — draft/rewrite/summarize/classify/extract N items, LLM-as-judge, embeddings-style fan-out | CLIProxyAPI | No tools needed. Measured: agent CLIs spend ~5–7× the input tokens on harness boilerplate for pure-generation calls (cursor ~23k, droid ~15k overhead PER fresh spawn). The proxy sends only your payload. |
| One-off question / second opinion | either; agent CLI is fine | Overhead is negligible at N=1. |
Rule of thumb: if the task needs tools, use an agent CLI; if it's just model-in/text-out at volume, use the proxy. Measured basis: docs/x-outreach-design-style bulk drafting was ~85% harness tokens per batch through cursor-agent; the proxy eliminates that.
Setup
Build from source (Go 1.24+) or use the Docker image from CLIProxyAPI:
git clone --depth 1 https://github.com/router-for-me/CLIProxyAPI && cd CLIProxyAPI
go build -o ~/.local/bin/cliproxy ./cmd/server
mkdir -p ~/.cliproxy/auths
Write ~/.cliproxy/config.yaml (localhost-only recommended):
host: "127.0.0.1" # localhost-only; do not expose to the network
port: 8317
auth-dir: "~/.cliproxy/auths"
api-keys:
- "sk-local-<generate-your-own>" # clients send this as Bearer token
remote-management:
allow-remote: false
secret-key: "<generate-your-own>"
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.
- 7d ago First seen · 84 lines · 103 tokens per session scan A 3feeab0ac6d9
use-cliproxy is a skill published in the GitHub repository contains-studio/fable-delegator (12 stars, last pushed 1mo ago), licensed MIT. It adds 103 tokens to every session and 1,434 once invoked, about $0.0005 per session on Opus 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
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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…