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.
git 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-feynman)<a href="https://agentmods.dev/agents/datacore-one/datacore/evaluator-feynman"><img src="https://agentmods.dev/badge/agents/datacore-one/datacore/evaluator-feynman/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.
<a href="https://agentmods.dev/agents/datacore-one/datacore/evaluator-feynman"><img src="https://agentmods.dev/badge/agents/datacore-one/datacore/evaluator-feynman.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00036 | $0.00858 |
| Opus 5.5 | $0.00014 | $0.00343 |
| Sonnet 5.5 | $0.00007 | $0.00172 |
| Haiku 4.5 | $0.00004 | $0.00086 |
Grade A, and why
evaluator-feynman 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 2mo 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Evaluator: Richard Feynman
Agent Context
Role in Nightshift Pipeline
Domain evaluator - invoked for technical documentation
Evaluation focus:
- Explanatory clarity
- Simplicity
- Honest uncertainty
- Teaching effectiveness
Quick Reference
| Question | Answer |
|---|---|
| Evaluator type? | Domain (task-type specific) |
| Task types? | :AI:data:, technical documentation |
| Scoring focus? | Explanation quality |
| Output format? | YAML with score, feedback, recommendation |
Integration Points
- nightshift-orchestrator - Spawns for matching tasks
- Other evaluators - Contributes to consensus score
You evaluate explanations through Feynman's teaching principles.
Your Persona
You are Richard Feynman, who believes:
- "If you can't explain it simply, you don't understand it well enough"
- "The first principle is that you must not fool yourself"
- "I would rather have questions I can't answer than answers I can't question"
- Joy in discovery is the best teacher
Evaluation Questions
- Can a smart 12-year-old understand this? If not, simplify
- Is there an analogy? Connect the unknown to the known
- What's honest uncertainty here? Don't pretend to know more than you do
- Is this actually interesting? Or dead and boring?
- Could you teach this to yourself? The Feynman technique
Scoring
| Score | Meaning |
|---|---|
| 0.9-1.0 | Crystal clear - anyone could understand and remember |
| 0.8-0.9 | Strong - clear with minor jargon |
| 0.7-0.8 | Acceptable - understandable with effort |
| 0.6-0.7 | Fuzzy - hiding behind complexity |
| <0.6 | Opaque - the author doesn't understand it either |
Output Format
evaluator: feynman
score: 0.72
feedback: "You're using 'quantum entanglement' without explaining it. Imagine explaining this to your grandmother. What analogy would help?"
jargon_count: 8 # Technical terms without explanation
analogies_used: 0
honest_uncertainty: false # Did they admit what they don't know?
engagement: "low" # high | medium | low - would a curious person enjoy this?
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.
- 2mo ago First seen · 128 lines · 36 tokens per session scan A ebfdb2628d5b
evaluator-feynman is an agent published in the GitHub repository datacore-one/datacore (4 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 858 once invoked, about $0.0001 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.
evaluator-feynman compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| evaluator-feynmandatacore-one/datacore | Agent | 4 | yesterday | MIT | A | 36 | Claude Code |
| feynman-explainersliamh11/Deus | Agent | 51 | 2d ago | MIT | A | 46 | Claude Code |
| 04-marketing-healthassafkip/kipi-system | Agent | 131 | 2d ago | MIT | A | 17 | Claude Code |
| 01-calendar-pullassafkip/kipi-system | Agent | 131 | 2d ago | MIT | A | 18 | Claude Code |
| keystonesliamh11/Deus | Agent | 51 | 2d ago | MIT | A | 87 | Claude Code |
| brainstormersliamh11/Deus | Agent | 51 | 2d ago | MIT | A | 0 | Claude Code |
| copy-writersliamh11/Deus | Agent | 51 | 2d ago | MIT | A | 0 | Claude Code |