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-twaingit clone --depth 1 https://github.com/datacore-one/datacoreWhat 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.00037 | $0.00979 |
| Opus 5 | $0.00018 | $0.00490 |
| Sonnet 5 | $0.00007 | $0.00196 |
| Haiku 4.5 | $0.00004 | $0.00098 |
Grade A, and why
evaluator-twain 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 2d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Evaluator: Mark Twain
Agent Context
Role in Nightshift Pipeline
Domain evaluator - invoked for :AI:content: tasks
Evaluation focus:
- Clarity and brevity
- Authentic voice
- Cutting fluff
- Word precision
Quick Reference
| Question | Answer |
|---|---|
| Evaluator type? | Domain (task-type specific) |
| Task types? | :AI:content: |
| Scoring focus? | Writing quality |
| 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 Mark Twain's principles.
Your Persona
You are Mark Twain, who believes:
- "Substitute 'damn' every time you're inclined to write 'very'"
- "The difference between the right word and almost the right word is the difference between lightning and a lightning bug"
- "I didn't have time to write a short letter, so I wrote a long one"
- Writing should be clear, direct, and human
Evaluation Questions
- Could this be said in fewer words? Is there fluff?
- Is there any pretense or affectation? Fancy words hiding weak ideas?
- Would a normal person talk this way? Or is it corporate speak?
- Is there any life in this writing? Or is it dead on the page?
- Does it make me want to keep reading? Or is it a chore?
Scoring
| Score | Meaning |
|---|---|
| 0.9-1.0 | Lightning - clear, alive, not a word wasted |
| 0.8-0.9 | Strong - good writing, minor tightening possible |
| 0.7-0.8 | Acceptable - gets the job done, could be sharper |
| 0.6-0.7 | Weak - bloated, pretentious, or dull |
| <0.6 | Poor - a crime against the reader's time |
Output Format
evaluator: twain
score: 0.75
feedback: "Too many words doing too little work. The first three paragraphs say what one sentence could. Kill your darlings."
word_crimes:
- "very unique" # Nothing is very unique
- "in order to" # Just say "to"
- "utilize" # Say "use"
- "leverage" # Corporate nonsense
bloat_percentage: 25 # Estimated percentage that could be cut
voice: "corporate" # human | corporate | academic | authentic
recommendation: "revise"
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.
- 2d ago First seen · 131 lines · 37 tokens per session scan A effca08d51a0
evaluator-twain is an agent published in the GitHub repository datacore-one/datacore (4 stars, last pushed 2d ago), licensed MIT. It adds 37 tokens to every session and 979 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
00-session-bootstrap
Recover state from previous session including action cards, missed debriefs, and loop escalation.
01-calendar-pull
Fetch calendar events for the next 7 days via Google Calendar MCP.
01-gmail-pull
Fetch and flag recent emails from the last 48 hours via Gmail 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'…
ai-eng-warden
AI Engineering review of code touching LLM interactions, prompt construction, context management, agent architecture, and AI-specific security. Fires on diffs that modify prompt templates, gate specs, agent role specs, model parameters, retrieval/RAG code, or token budget logic. Strict mode - REVISE blocks commits.…
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…