writing-docs

A writing guide for documentation stored in the packages/docs folder. It explains GitBook Markdown, page structure, special content blocks, and the SUMMARY.md contents list.

In plain words
What is it for?
Use it to write or edit user manuals, documentation pages, and GitBook files.
Why use it?
It helps keep documentation pages and the documentation contents list in the format the project expects.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/nukeop/nuclear/writing-docs
Any agent
npx skills add nukeop/nuclear --skill writing-docs
Clone the repo
git clone --depth 1 https://github.com/nukeop/nuclear

Made for: Claude Code, Codex.

Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 881 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00057 $0.00881
Opus 5 $0.00028 $0.00441
Sonnet 5 $0.00011 $0.00176
Haiku 4.5 $0.00006 $0.00088

Measured 2d ago against content hash efc3694f80a4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

writing-docs 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 2d 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.

.agents/skills/writing-docs/SKILL.md · 173 lines

The source is not reproduced here

Licensed AGPL-3.0

The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

Changes

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.

  1. 2d ago First seen · 173 lines · 57 tokens per session scan A efc3694f80a4

Subscribe to this mod's changes

writing-docs is a skill published in the GitHub repository nukeop/nuclear (18,364 stars, last pushed 2d ago), licensed AGPL-3.0. It adds 57 tokens to every session and 881 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.

Related

Other skills, from other repositories

musicbox

Use when the user wants to play/pause/skip music, control volume, seek, search songs/playlists, query NetEase Music data, or operate NetEase MusicBox. Drives MusicBox through the musicbox CLI + daemon; never simulates terminal keypresses to the curses TUI.

darknessomi/musicbox · 65 tokens

hypersyn

How to author procedural content in orkid using HyperSyn (Reality Synthesizer) — a Python-as-DSL system for composing particle systems, 2D/3D procedural textures, mesh/SDF operations, and (eventually) audio/sequencer graphs into compact runtime experiences. Use when the user asks about HyperSyn, ptex2d, ptex3d…

tweakoz/orkid · 108 tokens

orkid

Answer questions about the orkid media engine. Routes to specialized sub-skills for threading, reflection, filesystem, graphics, UI, audio, ECS, asset catalog, Python bindings, application framework, FSM, subsystems, and EzApp. Use for any orkid question including architecture overview, build system, or cross-cutting…

tweakoz/orkid · 70 tokens

orklev2-audio

Answer questions about orkid's Singularity synthesizer engine, DSP processing, oscillators, filters, envelopes, modulation, sampling, FM synthesis, audio output, and program/bank structure. Use when the user asks about audio, synth, DSP, or sound.

tweakoz/orkid · 59 tokens

orklev2-coreaudio

Answer questions about orkid's CoreAudio backend (macOS), AudioUnit graph, HAL input/output callbacks, AuContext, CoreAudioDevice, stereo fragment pools, and how CoreAudio drives the Singularity synth engine. Use when the user asks about CoreAudio, AudioUnit, or macOS audio output.

tweakoz/orkid · 68 tokens

orklev2-alsa

Answer questions about orkid's ALSA audio backend (Linux), dual-thread architecture (ALSA thread + synth thread), PCM device configuration, multi-buffer producer/consumer queues, int16 interleaving, and how ALSA drives the Singularity synth. Use when the user asks about ALSA or Linux audio output.

tweakoz/orkid · 70 tokens