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 jykim/claude-obsidian-skills --skill interactive-writing-assistantgit clone --depth 1 https://github.com/jykim/claude-obsidian-skillsWrote 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/jykim/claude-obsidian-skills/interactive-writing-assistant)<a href="https://agentmods.dev/skills/jykim/claude-obsidian-skills/interactive-writing-assistant"><img src="https://agentmods.dev/badge/skills/jykim/claude-obsidian-skills/interactive-writing-assistant/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/jykim/claude-obsidian-skills/interactive-writing-assistant"><img src="https://agentmods.dev/badge/skills/jykim/claude-obsidian-skills/interactive-writing-assistant.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 Output Handling · line 97 Output size or generation rate is not bounded. Unbounded output enables denial-of-service through resource exhaustion, log flooding, or context-window stuffing.Fix: Set explicit limits on output length, generation count, and rate. Use max_tokens and truncation to prevent unbounded output.
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.00069 | $0.01613 |
| Opus 5 | $0.00034 | $0.00807 |
| Sonnet 5 | $0.00014 | $0.00323 |
| Haiku 4.5 | $0.00007 | $0.00161 |
Grade A, and why
interactive-writing-assistant 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 11d 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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interactive Writing Assistant
Overview
This skill supports all stages of the writing process through interactive collaboration with the user. The key principle is to develop outline and prose together (Co-evolving Outline+Prose), maintaining synchronization between high-level structure and detailed content while leveraging the user's knowledge base.
Core Principles
Co-evolving Outline+Prose (COP)
Develop outline and prose together for any piece to evolve both the big picture (via outline) and details (prose) while keeping them in sync.
Format structure:
## Section Title
%%
- Outline point 1
- Outline point 2
%%
Detailed prose goes here...
COP Guidelines:
- When given work with only outline (or prose), fill in the other
- When updating outline, also update corresponding prose (and vice versa)
- Place prose immediately below its outline (never separate them)
Voice-based User Input (VUI)
User input may come via voice interface, combining commands and content that need parsing before action.
VUI Examples:
Let's continue writing:
[content to be processed via IVT]
Let's improve this:
1. Remove all references of XYZ from writing
2. Change the style to the like of Haruki
VUI Processing:
- Parse commands from content
- Process voice content through Improve Voice Transcript (IVT) prompt
- Find user comments within markdown or HTML comments (%% %%)
- Mark comments as
RESOLVEDwhen addressed
Connected and Living Document (CLD)
Every piece is written as part of a PKM system, connected to other knowledge notes. Tap into this rich Information and Knowledge (INK) throughout the writing process, particularly in:
- Ideation Helper (IDH)
- Outline Expander (OEX)
- Devil's Advocate (DAV)
Keep the outcome document up-to-date as new INK is received.
Style References
Apply specific writing styles when requested. You can create style guides in references/ folder:
- Style guides describe tone, vocabulary, sentence structure preferences
- Load the appropriate style guide when user requests a specific style
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.
- 11d ago First seen · 242 lines · 69 tokens per session scan A c9f4e8b83c1c
interactive-writing-assistant is a skill published in the GitHub repository jykim/claude-obsidian-skills (50 stars, last pushed 19d ago), licensed MIT. It adds 69 tokens to every session and 1,613 once invoked, about $0.0003 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-30.
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…