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 agentmods add skills/reluctantfuturist/loyal-wingman/plot-threadsnpx skills add reluctantfuturist/loyal-wingman --skill plot-threadsgit 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/plot-threads)<a href="https://agentmods.dev/skills/reluctantfuturist/loyal-wingman/plot-threads"><img src="https://agentmods.dev/badge/skills/reluctantfuturist/loyal-wingman/plot-threads.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.00037 | $0.01605 |
| Opus 5 | $0.00018 | $0.00803 |
| Sonnet 5 | $0.00007 | $0.00321 |
| Haiku 4.5 | $0.00004 | $0.00161 |
Grade A, and why
plot-threads 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 6d 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 — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plot Threads
Track narrative threads (mysteries, questions, foreshadowing, Chekhov's guns) across a book.
The Iron Law
PROPOSE, DON'T IMPOSE. Read scene, suggest thread updates, wait for user confirmation before editing.
When to Use
- Called by query-context (Query mode) - before drafting
- Called by writing-mode Phase 6 (Update mode) - after drafting
- "check threads" / "what's unresolved" / "thread audit"
- Before marking final chapter complete
Thread Storage
Threads live in the project index file:
10_Projects/[Book Name]/[Book Name] Index.md
Table Structure
## Plot Threads
| Thread | Type | Scope | Introduced | Status | Scenes |
|--------|------|-------|------------|--------|--------|
| Gagik's true nature | Mystery | Series | Ch1 | Developing | Ch1, Ch3, Ch4 |
| Sorochan breach | Question | Book 1 | Ch2 | Resolved | Ch2, Ch3 |
| Gagik's specimens | Foreshadowing | Series | Ch3 | Planted | Ch3 |
| Ch1 job offer | Chekhov | Book 1 | Ch1 | Planted | Ch1 |
Thread Types
| Type | Description | Stale After |
|---|---|---|
| Mystery | Reader question, answered gradually | 4+ chapters |
| Question | Character question, resolved in-story | 2+ chapters |
| Foreshadowing | Planted for reread payoff | No warning |
| Chekhov | Object/detail that must pay off | End-of-book only |
Statuses
- Planted — Introduced but not yet developed
- Developing — Actively being explored
- Resolved — Paid off or answered
- Abandoned — Intentionally dropped
Scope
- Book 1 (or current book) — Must resolve before book ends
- Series — Can remain open across books
The Process
Query Mode (Before Drafting)
Called by query-context to surface relevant threads.
Phase 1: Locate Project Index
- Identify current project from scene path
- Find project index:
10_Projects/[Book]/[Book] Index.md - Read
## Plot Threadssection
If no Plot Threads section exists:
- Report: "No plot threads tracked yet. Create initial registry?"
- If user confirms, create empty table structure
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.
- 6d ago First seen · 230 lines · 37 tokens per session scan A 30b969eb08d1
plot-threads is a skill published in the GitHub repository reluctantfuturist/loyal-wingman (7 stars, last pushed 8mo ago), licensed MIT. It adds 37 tokens to every session and 1,605 once invoked, about $0.0002 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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…