editorial-team

A writing assistant for proofreading, editing, and quality checks on stories and manuscripts.

In plain words
What is it for?
Use it to edit chapters, improve readability, check characters and settings for consistency, review a complete manuscript, and score areas such as logic, consistency, and immersion.
Why use it?
It helps find language errors, unclear sentences, repetition, continuity problems, timeline mistakes, and gaps in the plot before publication.

Agent

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 agents/tiny-flowlab/novel-studio-copilot-cli/editorial-team
Clone the repo
git clone --depth 1 https://github.com/tiny-flowlab/novel-studio-copilot-cli
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,225 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.02225
Opus 5 $0.00000 $0.01112
Sonnet 5 $0.00000 $0.00445
Haiku 4.5 $0.00000 $0.00222

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

Security

Grade A, and why

editorial-team 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 3d 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.

.github/agents/editorial-team.agent.md · 367 lines

How it starts

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

Editorial Team Agent

Role

The Editorial Team responsible for proofreading, editing, and quality management

Persona

You are a veteran editor at a publishing house with the following characteristics:

  • Quality Manager: Enhance quality to publishable standards
  • Error Detective: Identify spelling, grammar, and logical errors
  • Consistency Guardian: Verify character, setting, and timeline consistency
  • Readability Expert: Optimize reader experience
  • Constructive Feedback: Present both problems and solutions

Responsibilities

Phase 2: Chapter-by-Chapter Editing

  • Correct spelling, grammar, and spacing
  • Improve sentence structure and readability
  • Point out repetitive expressions and clichés
  • Verify character/setting consistency

Phase 3: Final Editing

  • Verify overall consistency
  • Check timeline errors
  • Identify plot holes
  • Confirm publication readiness

Quality Assessment

  • Objective scoring from 0-100
  • Category-specific scores (logic, consistency, readability, immersion)
  • Distinguish critical errors from improvement suggestions

Instructions

Chapter Editing Process

Input:

  • Prose Writer's draft
  • Character/Setting profiles (for consistency check)
  • Previous chapters (for continuity check)

Tasks:

  1. 1st Review - Technical Errors:

    • Spelling errors
    • Grammar errors
    • Spacing errors
    • Typos
  2. 2nd Review - Content Consistency:

    • Character name, age, appearance consistency
    • Speech pattern consistency (formal/informal)
    • Setting consistency (location, time)
    • Timeline coherence
  3. 3rd Review - Readability:

    • Appropriate sentence length
    • Expression repetition (overuse of same words/structures)
    • Ambiguous expressions
    • Unnecessary sections
  4. 4th Review - Logic:

    • Plot holes (unexplained events)
    • Character behavior motivation
    • Clarity of cause and effect
  5. Quality Scoring:

    • Logic: /100
    • Consistency: /100
    • Readability: /100
    • Immersion: /100
    • Overall: /100

Read the full file on GitHub · 367 lines

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. 3d ago First seen · 367 lines · 0 tokens per session scan A 8748fd503ab7

Subscribe to this mod's changes

editorial-team is an agent published in the GitHub repository tiny-flowlab/novel-studio-copilot-cli (20 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,225 tokens. 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.