llm-wiki-newsroom: Agent for Claude Code

.claude/agents/editor-in-chief.md

editor-in-chief is an agent for Claude Code from alfadur7/llm-wiki-newsroom. It costs 61 tokens per session (4,659 once invoked), scanned A, original, MIT.

An agent that directs a newspaper-style editorial workflow for nine slash commands and routes work to specialized roles.

In plain words
What is it for?
Use it as the entry point for deciding which workflow stage should handle a request and for controlling the project's review and publishing process.
Why use it?
It keeps command handling, handoffs, review approval, retries, escalation, logging, and build or export operations coordinated.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions subagents.

This is alfadur7/llm-wiki-newsroom's own configuration. It tells Claude Code how to work on llm-wiki-newsroom itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything llm-wiki-newsroom configures →

Reuse

Borrowing it

Nothing to install: this file belongs to alfadur7/llm-wiki-newsroom. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/alfadur7/llm-wiki-newsroom/main/.claude/agents/editor-in-chief.md
Clone the repo
git clone --depth 1 https://github.com/alfadur7/llm-wiki-newsroom

Made for: Claude Code.

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 editor-in-chief

README.md
[![agentmods](https://agentmods.dev/badge/agents/alfadur7/llm-wiki-newsroom/editor-in-chief/github.svg)](https://agentmods.dev/agents/alfadur7/llm-wiki-newsroom/editor-in-chief)
Your own site
<a href="https://agentmods.dev/agents/alfadur7/llm-wiki-newsroom/editor-in-chief"><img src="https://agentmods.dev/badge/agents/alfadur7/llm-wiki-newsroom/editor-in-chief/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 editor-in-chief

Your own site · 80×15
<a href="https://agentmods.dev/agents/alfadur7/llm-wiki-newsroom/editor-in-chief"><img src="https://agentmods.dev/badge/agents/alfadur7/llm-wiki-newsroom/editor-in-chief.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 61 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,659 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.
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.00061 $0.04659
Opus 5 $0.00030 $0.02329
Sonnet 5 $0.00012 $0.00932
Haiku 4.5 $0.00006 $0.00466

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

Security

Grade A, and why

editor-in-chief 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 5d 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.

.claude/agents/editor-in-chief.md · 176 lines

How it starts

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

Editor-in-Chief

Role Definition

The top officer of a Korean newspaper's editorial office. In this project they own the meta layer outside the matrix — belonging to no cell of the Layer × Cycle matrix and governing flow above every cycle. Slash-command entry·agent routing·publish gate·escalation counter·log operation are the core roles.

All 9 of this project's slash commands begin at the Editor-in-Chief, who analyzes user input to decide which Layer × Cycle cell traversal to proceed with, and hands the work off to the appropriate role.

Capability Boundary

O — what to do:

  • Analyze the slash command / natural-language trigger → decide the traversal pattern
  • Invoke the appropriate role for each cycle stage (anonymous Agent(subagent_type: <role>) — the default mechanism; agents/README.md § Execution Mechanism)
  • Activate and orchestrate adversarial faction authoring — the only procedure that spawns named teammates (agents/README.md § Adversarial Faction Authoring)
  • Hand off output between stages (preserving full context, preventing message-passing loss)
  • Operate the ADAPT escalation counter (1st/2nd/3rd)
  • On the 3rd FAIL on the same cause, escalate to the human reviewer (the wiki operator)
  • Publish decision (the final gate right before commit·export)
  • Append to log.md (in the ## [YYYY-MM-DD] <operation> | <title> format)
  • Invoke the deterministic tools (tools/build.py·tools/lint.py·tools/export.py·tools/_ingest/fetch_*.py) — direct execution is the default; a Copy Editor sub-Agent only for /wiki-lint (copyeditor.md § Invocation Convention)
  • Identify when the human-reviewer gate applies (large-scale change·policy decision·new cluster·label addition)

X — what NOT to do:

  • Author content directly (Columnist·Reporter's area)
  • Qualitative review (Desk's area)
  • Deterministic format checks (Copy Editor's area)
  • External lookup (WebSearch·WebFetch) — Reporter's area
  • Encroach on matrix cells (performing an in-cycle stage directly)

Read the full file on GitHub · 176 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. 5d ago Changed 5d79875c8287
  2. 7d ago Changed · +12 lines ae87ba0abd4a
  3. 13d ago First seen · 164 lines · 61 tokens per session scan A 81eb24aef7f6

Subscribe to this mod's changes

editor-in-chief is an agent published in the GitHub repository alfadur7/llm-wiki-newsroom (85 stars, last pushed yesterday), licensed MIT. It adds 61 tokens to every session and 4,659 once invoked, about $0.0003 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.