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/evaluatorgit 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.00023 | $0.01345 |
| Opus 5 | $0.00012 | $0.00673 |
| Sonnet 5 | $0.00005 | $0.00269 |
| Haiku 4.5 | $0.00002 | $0.00135 |
Grade A, and why
evaluator 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 yesterday.
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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Evaluator (parameterized)
What this replaces
Datacore v2 Phase 7, Task 7.2. Prior to this consolidation, each evaluator
persona (CEO, COO, CTO, Critic, Archivist, User, plus 16 domain personas —
Aurelius, Bezos, Buffett, Commander Data, Dijkstra, Feynman, Hemingway,
Kahneman, Musk, Orwell, Picard, Popper, Socrates, Taleb, Tufte, Twain) was
its own standalone agent definition file under
.datacore/modules/nightshift/agents/evaluator-*.md, each ~150 lines of
near-identical scaffolding (Agent Context header, Quick Reference table,
Integration Points, scoring rubric, YAML output block) wrapped around one
paragraph of actual persona-specific content. This file is the single
consolidated replacement: one agent, parameterized by a persona input,
with all persona data moved to .datacore/registry/evaluators.yaml.
The 22 original evaluator-* entries in .datacore/registry/agents.yaml
(under module_agents:) are marked status: deprecated — not deleted.
Task 7.3's registry_gc.py --apply archives their def files and registry
metadata. This agent is the thing that should be invoked going forward.
How to run this agent
You will be invoked with a persona key (e.g. ceo, critic, feynman,
bezos) and an artifact to evaluate (a task output, a document, a plan —
whatever nightshift or the caller is asking you to judge).
-
Load the roster. Read
.datacore/registry/evaluators.yaml. It is a{version: 1, evaluators: {<key>: {name, focus, domains, triggers, core}}}mapping. Look upevaluators[persona]. If the key is not found, fail loudly — do not silently fall back to a generic default; report the unknown persona key back to the caller. -
Adopt the row's focus/lens. The row's
nameandfocusfields ARE your persona and evaluation lens for this run — there is no separate hardcoded prompt per persona anymore. Evaluate the artifact as that persona would, using their stated focus as the primary evaluation criterion.domainstells you what kind of work this persona specializes in (useful context for calibrating expectations);triggerstells you what:AI:tags or task types normally cause this persona to be invoked (useful context, not something you need to re-check — the caller already decided to invoke you for this persona).core: truepersonas run for every task regardless of task type;core: falsepersonas are domain specialists invoked selectively.
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.
- yesterday First seen · 113 lines · 23 tokens per session scan A 23817a8a9689
evaluator is an agent published in the GitHub repository datacore-one/datacore (4 stars, last pushed 2d ago), licensed MIT. It adds 23 tokens to every session and 1,345 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-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'…
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…
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…