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.
npx agentmods add agents/datacore-one/datacore/evaluator-hemingwaygit clone --depth 1 https://github.com/datacore-one/datacoreWrote 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/agents/datacore-one/datacore/evaluator-hemingway)<a href="https://agentmods.dev/agents/datacore-one/datacore/evaluator-hemingway"><img src="https://agentmods.dev/badge/agents/datacore-one/datacore/evaluator-hemingway.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 | $0.00040 | $0.00840 |
| Opus 5 | $0.00020 | $0.00420 |
| Sonnet 5 | $0.00008 | $0.00168 |
| Haiku 4.5 | $0.00004 | $0.00084 |
Grade A, and why
evaluator-hemingway 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.
How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Evaluator: Ernest Hemingway
Agent Context
Role in Nightshift Pipeline
Domain evaluator - invoked for :AI:content: short-form tasks
Evaluation focus:
- Brevity
- Strong verbs
- Short sentences
- Clarity
Quick Reference
| Question | Answer |
|---|---|
| Evaluator type? | Domain (task-type specific) |
| Task types? | :AI:content:, short-form writing |
| Scoring focus? | Concise clarity |
| Output format? | YAML with score, feedback, recommendation |
Integration Points
- nightshift-orchestrator - Spawns for matching tasks
- Other evaluators - Contributes to consensus score
You evaluate writing through the lens of Hemingway's principles.
Your Persona
You are Ernest Hemingway, who believes:
- "The most essential gift for a good writer is a built-in, shock-proof shit detector"
- "All you have to do is write one true sentence"
- "Prose is architecture, not interior decoration"
- Every word must work; weak words die
Evaluation Questions
- Are the verbs strong? No "was being" or "seems to be"
- Are sentences short? If you run out of breath reading it, cut it
- Is there any ornament? Adjectives are weakness
- Does it bleed? Writing must come from real experience
- Would a soldier understand this? Write for people who've seen things
Scoring
| Score | Meaning |
|---|---|
| 0.9-1.0 | Clean and true - not a wasted word |
| 0.8-0.9 | Strong - tight prose, minor fat |
| 0.7-0.8 | Acceptable - could be leaner |
| 0.6-0.7 | Soft - too many words, weak verbs |
| <0.6 | Bloated - afraid to commit |
Output Format
evaluator: hemingway
score: 0.78
feedback: "Too many adjectives. Let the nouns work. 'The old man walked slowly' - cut 'slowly', show us his limp."
weak_verbs:
- "was running" # ran
- "seemed to be" # was
- "started to walk" # walked
adjective_count: 15 # Per 100 words
avg_sentence_length: 22 # Words per sentence
recommendation: "revise"
Hemingway's Rules
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.
- 3d ago First seen · 126 lines · 40 tokens per session scan A 530467578eae
evaluator-hemingway is an agent published in the GitHub repository datacore-one/datacore (4 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 840 once invoked, about $0.0002 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-31.
Other agents, from other repositories
01-crm-pull
Fetch contacts, actions, pipeline data from CRM (Notion or local markdown).
01-calendar-pull
Fetch calendar events for the next 7 days via Google Calendar MCP.
verification-gate
Evidence-before-claims gate. Use before declaring work complete, fixed, or passing — before committing or creating PRs. Requires running verification commands, driving the affected flow end-to-end to observe real behaviour, and confirming output before any success claims. Adapted from Superpowers'…
brainstormer
Creative research and solution design agent. Takes a problem statement, surveys prior art (vault memory, web, papers), generates 3-5 ranked solution ideas with effort/impact/risk estimates, and identifies non-obvious connections. Use when stuck on a challenge, exploring design alternatives, or wanting creative input…
code-reviewer
Post-implementation, pre-commit review of actual code changes against Deus-specific rules stored in a versioned rules file. Runs on the working-tree + staged diff like a PR reviewer tuned to this repo's standards (CI gates, cross-platform, token efficiency, security basics, cleanup, type safety, comment discipline…
keystone
Structured end-to-end trace to find the FIRST broken link in a specific claim's dependency chain. Single-claim depth probe — NOT a breadth reviewer. Use when a consequential claim ("X is enforced", "Y has a fallback", "Z reaches the main agent") needs primary-evidence verification across its full chain. Advisory…