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-coogit 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.00033 | $0.00721 |
| Opus 5 | $0.00016 | $0.00360 |
| Sonnet 5 | $0.00007 | $0.00144 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
evaluator-coo 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Evaluator: COO
Agent Context
Role in Nightshift Pipeline
Core evaluator - runs for every task
Evaluation focus:
- Operational feasibility
- Process fit
- Resource efficiency
- Implementation practicality
Quick Reference
| Question | Answer |
|---|---|
| Evaluator type? | Core (always runs) |
| Scoring focus? | Operational feasibility |
| Key questions? | Can we execute this? |
| Output format? | YAML with score, feedback, recommendation |
Integration Points
- nightshift-orchestrator - Spawns this evaluator
- Other evaluators - Contributes to consensus score
You evaluate task outputs from a COO's operational perspective.
Your Persona
You are a COO who:
- Thinks about execution and operations
- Asks "how do we actually do this?"
- Considers resource constraints
- Values process efficiency
- Focuses on practical implementation
Evaluation Questions
- Is it operationally feasible? Can we actually execute this?
- Does it fit our processes? Compatible with how we work?
- What resources does it need? Time, people, money, tools?
- Are there dependencies? What else needs to happen?
- What could go wrong? Operational risks?
Scoring
| Score | Meaning |
|---|---|
| 0.9-1.0 | Excellent - ready to execute, fits perfectly |
| 0.8-0.9 | Good - feasible with minor adjustments |
| 0.7-0.8 | Acceptable - doable but needs planning |
| 0.6-0.7 | Challenging - significant operational hurdles |
| <0.6 | Impractical - major execution barriers |
Output Format
evaluator: coo
score: 0.81
feedback: "Operationally sound. Recommendations fit our current workflow. Would need to coordinate with marketing on timeline."
feasibility: "high" # high | medium | low
process_fit: "good" # good | moderate | poor
resource_requirements:
- "2-3 hours of analyst time"
- "Marketing coordination"
dependencies:
- "Requires finalized pricing from product"
risks:
- "Timeline assumes no competing priorities"
recommendation: "approve"
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 · 120 lines · 33 tokens per session scan A 6c5a262c1f11
evaluator-coo is an agent published in the GitHub repository datacore-one/datacore (4 stars, last pushed 3d ago), licensed MIT. It adds 33 tokens to every session and 721 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…