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 Natsummerance/readMD --skill writing-staffinggit clone --depth 1 https://github.com/Natsummerance/readMDWrote 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/natsummerance/readmd/writing-staffing)<a href="https://agentmods.dev/skills/natsummerance/readmd/writing-staffing"><img src="https://agentmods.dev/badge/skills/natsummerance/readmd/writing-staffing.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00047 | $0.01088 |
| Opus 5 | $0.00023 | $0.00544 |
| Sonnet 5 | $0.00009 | $0.00218 |
| Haiku 4.5 | $0.00005 | $0.00109 |
Grade A, and why
writing-staffing 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 8d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Staffing
Each agent loads its core skills from its YAML. This skill teaches what extra to attach and reference when spawning.
Model Selection
Agent defaults are usually correct. When overriding or selecting models for additional lanes, match the model to the work:
sol: taste, judgment, creative generation, and high-stakes critiqueterra: structured synthesis, outlining, and cross-document checkingluna: mechanical information gathering and explorationdeepseekflash: the cheapest acceptable lane for bulk gathering or mechanical checks where misses can be caught during synthesis
For model-diverse fan-out, choose one available Claude-family model and one
available Codex-family model. Check meridian mars models list at dispatch
time rather than assuming which concrete model an alias currently resolves to.
Fan-out means giving the same question and files to different model families for independent judgment. Reserve it for high-stakes calls where model diversity can reveal different blind spots. Parallel lanes use different prompts or focus areas; use each agent's default model unless a lane needs a capability it lacks.
Dispatch Reference
@writer
Extra --skills: character-sim for voice fidelity, shared-dao for
project vocabulary.
Reference in prompt: name the production mode from /creative-writing-modes
→ resources/prose-modes.md (fresh draft, revision, bridge, alternate take,
line polish). Point to /creative-writing-craft → resources/prose-writing.md
or resources/scene-construction.md when relevant. Attach style files,
character state, and continuity anchors via -f.
One writer per scene — voice consistency degrades when multiple writers handle adjacent content.
@critic
Extra --skills: creative-writing-craft for prose/voice focus,
shared-dao for vocabulary checks.
Reference in prompt: assign a focus area (structure, character, voice, prose,
or continuity). Attach style files via -f for voice critique.
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.
- 8d ago First seen · 138 lines · 47 tokens per session scan A cc3e89eab143
writing-staffing is a skill published in the GitHub repository Natsummerance/readMD (22 stars, last pushed 4d ago), licensed MIT. It adds 47 tokens to every session and 1,088 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-30.
Other skills, from other repositories
gonavi-cli
Operate databases through the GoNavi headless CLI — the gonavi executable shipped in verified GitHub Release archives. Covers listing/adding/importing saved connections, running SQL queries against saved connections or ad-hoc connection files, exporting result sets to csv/json/md/html/xlsx, batch-executing SQL files…
bibverify
Verify, repair, explain, and generate BibTeX references with Bibverify's DOI-first CLI and MCP tools.
electron-expert
Expert in Electron framework, desktop app development, IPC, and cross-platform packaging. Use when the user mentions desktop, Node.js, cross platform, Windows, macOS, or Linux, or when the task involves Electron Architecture, Process Types, IPC Communication, or App Lifecycle.
memory
Use this skill when Pioneer should proactively use durable memory or recalled context: decide whether memory can improve a turn, answer from remembered user/project facts, request memory tools, search/list/get stored memories, save durable preferences or project decisions, forget memories, audit or clean up memory, or…
trellis-brainstorm
Guides collaborative requirements discovery before implementation. Creates task directory, seeds PRD, asks high-value questions one at a time, researches technical choices, and converges on MVP scope. Use when requirements are unclear, there are multiple valid approaches, or the user describes a new feature or complex…
trellis-update-spec
Captures executable contracts and coding conventions into .trellis/spec/ documents. Use when learning something valuable from debugging, implementing, or discussion that should be preserved for future sessions.