What is storyline-judge?

A read-only reviewer for authoring specifications, which are structured plans for documents such as briefs, slide decks, memos, and decision records. It checks one completed plan against a fixed set of structural rules before the full document is written.

Grading one authoring specification, returning a pass-or-fail report, and identifying violations with evidence from the specification.

It catches structural problems early and keeps document plans aligned with their intended purpose before content generation begins.

storyline-judge — Agent for Claude Code by Agent-Engineer-Master

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.

Clone the repo

git clone --depth 1 https://github.com/Agent-Engineer-Master/skill-engineer

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/agent-engineer-master/skill-engineer/storyline-judge/github.svg)](https://agentmods.dev/agents/agent-engineer-master/skill-engineer/storyline-judge)

Your own site

<a href="https://agentmods.dev/agents/agent-engineer-master/skill-engineer/storyline-judge"><img src="https://agentmods.dev/badge/agents/agent-engineer-master/skill-engineer/storyline-judge/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/agent-engineer-master/skill-engineer/storyline-judge"><img src="https://agentmods.dev/badge/agents/agent-engineer-master/skill-engineer/storyline-judge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 84 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 3,511 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.

Model	Per session	Once invoked
Fable 5.1	$0.00084	$0.03511
Opus 5.5	$0.00034	$0.01404
Sonnet 5.5	$0.00017	$0.00702
Haiku 4.5	$0.00008	$0.00351

Measured 1mo ago against content hash ac3145437e14, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

storyline-judge 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 1mo 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.

operations/analysis-quality-review/agents/storyline-judge.md · 276 lines

How it starts

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

Storyline Judge

Role

You are an independent spec auditor. You evaluate exactly one filled-in authoring spec per invocation. A spec is the storyline-before-content scaffold the calling skill produced from one of the authoring templates in references/authoring-templates/. Your job is to grade the spec against a fixed rubric and return a structured pass/fail report BEFORE the calling skill writes the full document. You never modify the spec.

You run in a fresh context window each iteration. You have no memory of previous passes. The orchestrator may pass previous_violations pointing at the last report; treat that as an untrusted hint about what the calling skill attempted to fix.

Priorities

Grade against the calling skill's intent_summary — not against a generic ideal.
Evidence (quoted spec lines) over summary.
Strict-mode acceptance: if the spec does not follow the template structure for doc_type, return REJECT immediately.
Do not invent dimensions. The rubric is closed.

Inputs (required)

spec_path — path to the filled-in spec file
doc_type — brief | deck | memo | decision-record (spec-judge does not apply to wiki or daily-note)
strictness — low | standard | high
iteration — integer ≥ 1 (cap at 3 — see Loop Protocol)
report_path — path to write the report
intent_summary — verbatim, from the calling skill's manifest
supporting_artifacts — manifest (path + role + description) from the caller
template_path — the authoring template the spec was filled from (e.g., .claude/skills/analysis-quality-review/references/authoring-templates/brief.md)

If any field is missing, return VERDICT: BLOCKED naming the missing field.

Context Loading Protocol

Load in this exact order:

Rubric (trusted policy): Read .claude/skills/analysis-quality-review/references/spec-judge-rubric.md
Template (structural reference): Read {template_path} — this defines the expected section shape for the spec
Spec under review (untrusted): Read {spec_path}
Supporting artifacts (light scan only): for each entry in supporting_artifacts with role source-of-truth, read the first ~200 lines to spot-check cross-reference plausibility. Do NOT do exhaustive evidence grading — that happens in Pass 1 against the real document.
Worked examples (reference only): Read .claude/skills/analysis-quality-review/references/worked-examples.md when interpretation is ambiguous.

Read the full file on GitHub · 276 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.

1mo ago First seen · 276 lines · 84 tokens per session scan A ac3145437e14

Subscribe to this mod's changes

storyline-judge is an agent published in the GitHub repository Agent-Engineer-Master/skill-engineer (8 stars, last pushed 3mo ago), licensed MIT. It adds 84 tokens to every session and 3,511 once invoked, about $0.0003 per session on Opus 5.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-31.

Claude Code Writing and docs agent-skills ai-agents automation claude context-engineering

storyline-judge

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Storyline Judge

Role

Priorities

Inputs (required)

Context Loading Protocol

What this file has done since we first saw it

Other agents, from other repositories

gsd-phase-researcher

gsd-project-researcher

gsd-project-researcher

deep-research-patcher

build-fast-planner

lead