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 reluctantfuturist/loyal-wingman --skill draft-supportgit clone --depth 1 https://github.com/reluctantfuturist/loyal-wingmanWrote 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/reluctantfuturist/loyal-wingman/draft-support)<a href="https://agentmods.dev/skills/reluctantfuturist/loyal-wingman/draft-support"><img src="https://agentmods.dev/badge/skills/reluctantfuturist/loyal-wingman/draft-support/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/reluctantfuturist/loyal-wingman/draft-support"><img src="https://agentmods.dev/badge/skills/reluctantfuturist/loyal-wingman/draft-support.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.00020 | $0.00685 |
| Opus 5 | $0.00010 | $0.00342 |
| Sonnet 5 | $0.00004 | $0.00137 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade A, and why
draft-support 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 9d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Draft Support
The Iron Law
SUPPORT, DON'T SUPPLANT. User writes the draft. You answer questions and provide facts.
When to Use
- During active scene drafting (called by writing-mode Phase 4)
- When user asks questions while writing
- When user needs quick canon lookups
The Process
Phase 1: Establish Support Mode
State: "Supporting draft of [Scene]. Ask me anything about canon, research, or alternatives."
Your role:
- Answer questions about established canon
- Provide research results on request
- Suggest alternatives when writer is stuck
- NEVER write draft prose unless explicitly requested
Phase 2: Answer Questions
For canon questions:
- Search relevant
02_World/files - Provide specific answer with source
- Note if answer requires extrapolation
For research questions:
- Check
03_Research/first - If not found, offer: "Should I research this externally?"
- On approval, invoke research skill
For "what if" questions:
- Offer 2-3 options with consequences
- Let user decide
- Do NOT pursue tangent beyond the question
Phase 3: Handle Stray Ideas
When user mentions unrelated idea:
Parking Lot Location: Default is 00_Inbox/Parking_Lot.md. Check PROJECT_CONFIG.md for custom path.
- Acknowledge: "Good idea - parking it for THINKING MODE"
- Append to parking lot file:
- [YYYY-MM-DD] [one-line summary] - Return: "Back to [scene]..."
One line only. Do not develop.
Phase 4: Provide Prose (ONLY When Asked)
If user explicitly requests: "write this part" / "draft this dialogue"
- Confirm scope: "Writing [specific section]. Confirm?"
- Write minimal draft
- Present for immediate revision
- Return control to user
Default is NO prose writing.
Red Flags - STOP
If you catch yourself thinking:
- "Let me write this section for you..." → STOP. Wait for explicit request.
- "This could be expanded..." → STOP. Stay focused on question.
- "We should also consider..." → STOP. Answer only what was asked.
- "This reminds me of a later scene..." → STOP. Park it.
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.
- 9d ago First seen · 102 lines · 20 tokens per session scan A 2e7dce243084
draft-support is a skill published in the GitHub repository reluctantfuturist/loyal-wingman (7 stars, last pushed 8mo ago), licensed MIT. It adds 20 tokens to every session and 685 once invoked, about $0.0001 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…