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 alfredxw/denova --skill novel-standardgit clone --depth 1 https://github.com/alfredxw/denovaWrote 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/alfredxw/denova/novel-standard)<a href="https://agentmods.dev/skills/alfredxw/denova/novel-standard"><img src="https://agentmods.dev/badge/skills/alfredxw/denova/novel-standard/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/alfredxw/denova/novel-standard"><img src="https://agentmods.dev/badge/skills/alfredxw/denova/novel-standard.svg" alt="Reviewed on agentmods" width="80" 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.00031 | $0.01017 |
| Opus 5 | $0.00015 | $0.00508 |
| Sonnet 5 | $0.00006 | $0.00203 |
| Haiku 4.5 | $0.00003 | $0.00102 |
Grade A, and why
novel-standard 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 7d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
novel-standard
Use this standard Writing Agent workflow to balance quality and speed.
Determine the writing scope
- Infer the scope from the user's actual request, such as continuing a passage, writing a scene, one chapter, three chapters, a short story arc, or a custom target.
- Do not assume the task is the next chapter unless the user explicitly asks for it.
- There is no
writing_scopefield. The user message is the sole source for scope, goal, constraints, and output form. - When the user requests N chapters or another multi-part deliverable, first make a concise overall and per-chapter plan to guide the draft.
Workflow
main Agent drafts -> general-purpose SubAgent reviews -> main Agent revises and updates state -> final output
Use only the main Agent and the built-in general-purpose SubAgent. Do not assume other named SubAgents exist or start additional writing subprocesses. If the task tool is unavailable or general-purpose cannot be used, the main Agent performs the same review itself and must not fabricate delegation or review results.
Tool requirements
- Before writing, use
readfor the necessary context:CREATOR.md,setting/outline.md,setting/progress.md,setting/character-states.md, the relevant chapter-group plan, and recent chapters. For lore, uselist_lore_itemsto identify relevant entries andread_lore_itemsto load their complete bodies. - After drafting, use
writeto create the correctly named chapter file underchapters/. For a localized revision to an existing chapter, useedit;old_stringmust match the current file exactly and uniquely and must not contain line-number prefixes returned byread. - When available, delegate review to
general-purposethroughtask. Its description must state the user's goal, chapter path, necessary context sources, review focus, output format, and that the SubAgent reviews only and must not modify files. - After review, use
writefor a complete chapter replacement oreditfor a few localized changes. Apply the same localized-edit versus complete-rewrite rule tosetting/progress.mdandsetting/character-states.md. - Inspect every
writeoreditresult. If it contains[tool error], invalid JSON arguments,string not found, a non-unique match, a path error, or a truncation notice, do not claim completion. Reread the target, correct the arguments, and retry, or clearly report that the write did not succeed. - Before the final response, use
readto verify key excerpts from every new or revised chapter and from any updated state files.
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.
- 7d ago Changed 438d130332ef
- 12d ago First seen · 51 lines · 31 tokens per session scan A 288b8dbfbc67
novel-standard is a skill published in the GitHub repository alfredxw/denova (713 stars, last pushed today), licensed Apache-2.0. It adds 31 tokens to every session and 1,017 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
llmlint
A Chinese-prose rule library with two entry points. Before writing, emit the rules as writing constraints to load into a system prompt or style guide. After writing, lint the draft with static rule hits, neural AIGC heatmaps, contextual review, approved repair, and local learning notes. Use when drafting or rewriting…
profile-system-guide
Guide users and agents through Neuro Book harness, TSX profiles, ProfileTurnPlan, skills, user-assets overlays, settings forms, profile home resources, profile compile checks, templates, system restore, and safe profile editing.
novel-technique-character-card-workshop
A workshop for turning rough character ideas into detailed, usable character profiles. It supports structured question cycles, personality layers, visual themes, and checks against reducing a character to a few labels.
RP模式
A set of instructions for running a role-playing session under the NeuroBook RP protocol. RP means role-play, where characters and events are simulated according to defined rules.
novel-writer-execution
An internal execution guide for a writer profile after it receives a brief. It describes the detailed workflow, decision points, and common mistakes.
novel-import-silly-tavern-card
A workflow for importing SillyTavern character cards and related role-playing materials into a NeuroBook project workspace. SillyTavern is software that stores character, world, and prompt data for role-play chats.