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 commands/datacore-one/datacore/diagnosticgit 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/commands/datacore-one/datacore/diagnostic)<a href="https://agentmods.dev/commands/datacore-one/datacore/diagnostic"><img src="https://agentmods.dev/badge/commands/datacore-one/datacore/diagnostic.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.00006 | $0.04725 |
| Opus 5 | $0.00003 | $0.02363 |
| Sonnet 5 | $0.00001 | $0.00945 |
| Haiku 4.5 | $0.00001 | $0.00473 |
Grade A, and why
diagnostic 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 today.
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 — 594 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Diagnostic
Command Context
When to Reference DIP-0002
Always reference when:
- Validating CLAUDE.md layer structure
- Checking module installation
- Verifying context file composition
- Auditing repository health
Key decisions this DIP informs:
- Layered context file pattern
- Expected directory structure
- Module installation verification
Quick Reference
| Question | Answer |
|---|---|
| Primary check? | Core matrix, repos, spaces |
| CLAUDE.md layers? | .base.md, .org.md, .local.md |
| What DIPs govern this? | DIP-0002 (Layered Context), DIP-0007 (Modules) |
Agents This Command Invokes
| Agent | Purpose |
|---|---|
context-maintainer |
Context validation |
structural-integrity |
Folder structure check |
Integration Points
- DIP-0002 - Layered context pattern
- DIP-0007 - Module specification
- /audit-agents - Registry audit complement
"All hands, this is the bridge. Prepare for full systems diagnostic."
Run a comprehensive diagnostic of all Datacore systems to verify installation health and operational status.
Behavior
Execute a Level 1 diagnostic sequence, checking all primary and secondary systems. Report status using TNG-style terminology.
Diagnostic Sequence
1. Primary Systems Check
Core Matrix:
- Verify
~/Dataexists and is accessible - Check
.datacore/directory structure - Verify CLAUDE.md present at root
Report format:
PRIMARY SYSTEMS
---------------
Core Matrix.............. [OPERATIONAL/OFFLINE]
- Root directory: [path]
- .datacore config: [PRESENT/MISSING]
- CLAUDE.md: [PRESENT/MISSING]
2. Repository Health
Check git status for all repositories:
| Repository | Location | Expected Remote |
|---|---|---|
| datacore (root) | ~/Data/ |
datacore-one/datacore |
| teamspace | ~/Data/1-teamspace/ |
datacore-one/teamspace |
| projectspace | ~/Data/2-projectspace/ |
datacore-one/projectspace |
| datacore-dips | ~/.datacore/dips/ |
datacore-one/datacore-dips |
| trading (module) | ~/.datacore/modules/trading/ |
datacore-one/datacore-trading |
| campaigns (module) | ~/.datacore/modules/campaigns/ |
datacore-one/campaigns |
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.
- today First seen · 594 lines · 6 tokens per session scan A 2721f43e897e
diagnostic is a command published in the GitHub repository datacore-one/datacore (4 stars, last pushed today), licensed MIT. It adds 6 tokens to every session and 4,725 once invoked, about $0.0000 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-09-03.
Other commands, from other repositories
prd-review
Review the active PRD with Codex and stream normalized findings to JSONL.
prd-archive
Archive the active PRD (blocked until every accepted finding has a receipt).
prd-map
Build a codebase map so PRDs are written with repo context, not blind.
prd-split
Split the approved PRD into one issue spec per manifest entry.
rca-check
Lint an RCA or premortem document against the canonical template.
prd-os-init
Initialize prd-os in this repo (writes .prd-os/config.json).