draft-marker-discipline

draft-marker-discipline is a skill for Codex from Boom5426/Nature-Paper-Skills. It costs 83 tokens per session (2,824 once invoked), scanned A, original, MIT.

A system for marking and managing unresolved questions directly inside a manuscript draft. It also covers counting words without those markers, archiving replaced text, and safely applying repeated edits.

In plain words
What is it for?
Use it when writing a manuscript across sessions or with several contributors, reviewing open questions, checking the true word count, removing superseded material, or making the same edit across many files.
Why use it?
Open questions kept only in chat or separate lists can be lost or become disconnected from the sentences they affect. In-source markers keep the draft's unfinished decisions visible and auditable.

Skill for Codex

Written for Codex: reads ~/.codex or $CODEX_HOME. Also seen: reads .claude/ paths; mentions Claude Code; mentions Codex.

Good fit Use it when writing a manuscript across sessions or with several contributors, reviewing open questions, checking the true word count, removing superseded material, or making the same edit across many files.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/boom5426/nature-paper-skills/draft-marker-discipline
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.

Any agent
npx skills add Boom5426/Nature-Paper-Skills --skill draft-marker-discipline
Clone the repo
git clone --depth 1 https://github.com/Boom5426/Nature-Paper-Skills

Made for: Codex.

Wrote 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.

agentmods badge for draft-marker-discipline

README.md
[![agentmods](https://agentmods.dev/badge/skills/boom5426/nature-paper-skills/draft-marker-discipline/github.svg)](https://agentmods.dev/skills/boom5426/nature-paper-skills/draft-marker-discipline)
Your own site
<a href="https://agentmods.dev/skills/boom5426/nature-paper-skills/draft-marker-discipline"><img src="https://agentmods.dev/badge/skills/boom5426/nature-paper-skills/draft-marker-discipline/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.

agentmods 80×15 button for draft-marker-discipline

Your own site · 80×15
<a href="https://agentmods.dev/skills/boom5426/nature-paper-skills/draft-marker-discipline"><img src="https://agentmods.dev/badge/skills/boom5426/nature-paper-skills/draft-marker-discipline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 83 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,824 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
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 Agent Snooping · line 139
    Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
    Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
How audits are shown
Origin original 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.1 $0.00083 $0.02824
Opus 5 $0.00042 $0.01412
Sonnet 5 $0.00017 $0.00565
Haiku 4.5 $0.00008 $0.00282

Measured 13d ago against content hash aa30d3fddeb0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

draft-marker-discipline 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 13d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/prose_wordcount.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/core/draft-marker-discipline/SKILL.md · 272 lines

How it starts

The opening of the file, as written. The whole thing — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Draft Marker Discipline

Overview

A manuscript written across many sessions accumulates open questions. Where those questions live determines whether the draft is auditable or merely long.

Kept in chat, they evaporate at the end of the session. Kept in a separate issue list, they drift out of sync with the sentence they belong to. Kept in the source next to the claim, they survive, they travel with the text, and they can be counted.

This skill covers the marker system, the triage that makes a marker count meaningful, the measurement that makes a length claim honest, and the two mechanical traps that have each cost a real build.

When To Use

Use this skill when:

  • a manuscript is drafted across sessions, by several people, or by agents
  • you are about to do a batch pass over open markers
  • you are about to quote the manuscript's length
  • superseded material needs to be removed from the tree
  • you are about to make the same edit across many files with a script

Do not use this skill for:

  • deciding whether a claim's source supports it. That is claim-source-verification; this skill is the bookkeeping around it.
  • restructuring an unstable argument. That is manuscript-optimizer.

1. Four Markers, Four Jobs

\TODO{...}        red     an unresolved FACTUAL or SOURCING question
\note{...}        blue    editorial, addressed to the authors
\directive{...}   boxed   what must change in this passage, and why
\superseded{...}  grey    text a freeze decision replaced, kept not deleted

All four vanish under a draft-mode switch, so a clean copy for circulation is one boolean away.

The discipline is the restriction on \TODO. It carries factual and sourcing questions only, never style notes, never "tighten this", never "consider rephrasing". Style goes in \note; a required change goes in \directive.

The payoff is that the \TODO count becomes a readiness metric rather than a mixed bag. "Thirty-seven open TODOs" means thirty-seven unresolved factual questions, which is a statement about the manuscript's evidentiary state. If style notes are mixed in, the number means nothing and stops being reported.

Read the full file on GitHub · 272 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 13d ago First seen · 272 lines · 83 tokens per session scan A aa30d3fddeb0

Subscribe to this mod's changes

draft-marker-discipline is a skill published in the GitHub repository Boom5426/Nature-Paper-Skills (490 stars, last pushed 7d ago), licensed MIT. It adds 83 tokens to every session and 2,824 once invoked, about $0.0004 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

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens