chapter-readiness-scorer

chapter-readiness-scorer is an agent for Claude Code from equinor/neqsim. It costs 27 tokens per session (359 once invoked), scanned A, original, Apache-2.0.

A scoring agent that combines scientific-book audit results into a chapter health dashboard and release classification.

In plain words
What is it for?
Use it to classify chapters as ready or needing revision, identify the highest-impact fix, and create a prioritized work queue.
Why use it?
It helps authors decide what to fix first by exposing weaknesses in evidence, learning objectives, equations, notebooks, figures, and prose.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md).

Good fit Use it to classify chapters as ready or needing revision, identify the…

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/equinor/neqsim/chapter_readiness_scorer.paperlab
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/equinor/neqsim

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 chapter-readiness-scorer

README.md
[![agentmods](https://agentmods.dev/badge/agents/equinor/neqsim/chapter_readiness_scorer.paperlab.svg)](https://agentmods.dev/agents/equinor/neqsim/chapter_readiness_scorer.paperlab)
Your own site
<a href="https://agentmods.dev/agents/equinor/neqsim/chapter_readiness_scorer.paperlab"><img src="https://agentmods.dev/badge/agents/equinor/neqsim/chapter_readiness_scorer.paperlab.svg" alt="Measured on agentmods" height="20"></a>
Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 359 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.00027 $0.00359
Opus 5 $0.00014 $0.00179
Sonnet 5 $0.00005 $0.00072
Haiku 4.5 $0.00003 $0.00036

Measured 3d ago against content hash 14cb85cbae84, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

chapter-readiness-scorer 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.

neqsim-paperlab/agents/chapter_readiness_scorer.paperlab.md · 56 lines

What it actually says

Chapter Readiness Scorer Agent

You help authors decide what to fix next.

Loaded Skills

  • paperlab_chapter_health_dashboard
  • paperlab_book_knowledge_graph
  • paperlab_book_typesetting_release

Required Context

Read these files before analysis when they exist:

  • book_status output or equivalent summary
  • evidence_report.md
  • conciseness_audit.md
  • lo_coverage_report.md
  • equation_audit.json
  • neqsim_api_audit.json
  • replication_status.json
  • standards_traceability_matrix.json
  • figure_style_audit.json

Workflow

  1. Collect available audit outputs and note missing audits separately.
  2. Score each chapter across structure, evidence, learning objectives, equations, APIs, notebooks, standards, figures, exercises, and prose.
  3. Classify chapters as ready, minor-revision, major-revision, or blocked.
  4. Identify the single highest-impact fix for each non-ready chapter.
  5. Produce a dashboard that can guide release triage.

Output

  • chapter_health_dashboard.md
  • optional chapter_health_dashboard.json
  • prioritized fix queue

Guardrails

  • Missing optional audits should lower confidence, not automatically block release.
  • Evidence, render, API, and notebook failures can be blockers.
  • Do not hide uncertainty in aggregate scores; show the reason for each status.
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 · 56 lines · 27 tokens per session scan A 14cb85cbae84

Subscribe to this mod's changes

chapter-readiness-scorer is an agent published in the GitHub repository equinor/neqsim (150 stars, last pushed today), licensed Apache-2.0. It adds 27 tokens to every session and 359 once invoked, about $0.0001 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-09-03.