Borrowing it
Nothing to install: this file belongs to TulanCN/vibe-noveling. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/TulanCN/vibe-noveling/main/CLAUDE.mdgit clone --depth 1 https://github.com/TulanCN/vibe-novelingWrote 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/instructions/tulancn/vibe-noveling/claude-md)<a href="https://agentmods.dev/instructions/tulancn/vibe-noveling/claude-md"><img src="https://agentmods.dev/badge/instructions/tulancn/vibe-noveling/claude-md.svg" alt="Measured on agentmods" height="20"></a>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.00799 | $0.00799 |
| Opus 5 | $0.00400 | $0.00400 |
| Sonnet 5 | $0.00160 | $0.00160 |
| Haiku 4.5 | $0.00080 | $0.00080 |
Grade A, and why
vibe-noveling CLAUDE.md 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Commands
- Search workflow contract text across shipped prompts:
rg -n "<pattern>" README.md plugins/vibe-noveling/skills plugins/vibe-noveling/agents
Architecture
This repository is a Claude Code plugin, not a traditional application. The main product surface is prompt contracts.
- Root
.claude-plugin/marketplace.jsonis the marketplace manifest. plugins/vibe-noveling/is the publishable plugin root.plugins/vibe-noveling/.claude-plugin/plugin.jsonholds plugin metadata.plugins/vibe-noveling/skills/contains the shipped workflow contracts, supporting references, and small Python tools.booming,fuck-it,novel-bookplan,novel-discuss,novel-init,novel-knowledge,novel-name,novel-progress,novel-snapshot,novel-sync,novel-write
plugins/vibe-noveling/agents/contains the built-in subagent prompts used by the writing workflow.consistency-guard(一致性校验),context-collector(上下文收集),writer-dazhongma(大仲马风),writer-zhouzi(会说话的肘子风)
README.mdis the public product and contributor guide; keep it aligned with shipped behavior.docs/plans/stores workflow design history and implementation notes. Search here before changing a workflow that may already have a recorded rationale.
Working Rules
- Treat prompt wording changes like code changes. In this repo, docs, prompt files, references, and tests are different projections of the same product behavior.
- Prefer edits under
plugins/vibe-noveling/when changing shipped behavior. - Update
README.mdwhenever user-facing workflow, installation, capabilities, or file layout changes. - Add or update
docs/plans/*.mdfor material workflow or design changes so future sessions can recover the rationale. - Do not assume
.claude/andplugins/vibe-noveling/are permanent mirrors. Confirm whether the task targets the local development copy, the shipped plugin, or both before editing.
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 · 56 lines · 799 tokens per session scan A 1d119102c50f
vibe-noveling CLAUDE.md is an instructions file published in the GitHub repository TulanCN/vibe-noveling (23 stars, last pushed 3mo ago), licensed MIT. It adds 799 tokens to every session, about $0.0040 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.