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/zayne-sprague/dr-claude-code/dashboard-syncgit clone --depth 1 https://github.com/Zayne-sprague/Dr-Claude-CodeWhat 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.00027 | $0.00727 |
| Opus 5 | $0.00014 | $0.00364 |
| Sonnet 5 | $0.00005 | $0.00145 |
| Haiku 4.5 | $0.00003 | $0.00073 |
Grade A, and why
dashboard-sync scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X POST "${DASHBOARD_URL}/api/experiments/sync" How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dashboard Sync
Sync experiment metadata, activity logs, and artifact references to the live Research Dashboard.
When to run
- After uploading any artifact to HuggingFace (so it appears in the Artifacts tab)
- After writing or updating experiment notes or activity logs
- After the harvest phase of an experiment pipeline
- After any change to experiment state (phase transitions, go/no-go decisions)
- When the user says "sync the dashboard", "update the website", or "refresh the dashboard"
Step 1: Check HUGGINGFACE_REPOS.md (if syncing a specific experiment)
If an experiment name was passed as an argument, read its artifact registry:
cat notes/experiments/<experiment_name>/HUGGINGFACE_REPOS.md 2>/dev/null
This confirms what HF datasets should appear in the Artifacts tab after sync.
Step 2: Run import_experiments.py
This reads all experiment data from notes/experiments/ — including configs, READMEs, activity logs, and HF repo lists — and uploads the aggregated data to the RESEARCH_DASHBOARD HF dataset.
cd tools/visualizer && .tools-venv/bin/python scripts/import_experiments.py
If the .tools-venv doesn't exist or the command fails:
# Fallback: use system python if venv is missing
cd tools/visualizer && python3 scripts/import_experiments.py
Capture the output. If it reports errors (missing files, HF auth failure), report them to the user.
Step 3: Trigger dashboard refresh
Tell the live HF Space to re-download the updated data:
# Dashboard URL is in .raca/config.yaml
DASHBOARD_URL=$(python3 -c "import yaml; print(yaml.safe_load(open('.raca/config.yaml'))['dashboard']['url'])" 2>/dev/null)
if [ -n "$DASHBOARD_URL" ]; then
curl -s -X POST "${DASHBOARD_URL}/api/experiments/sync"
else
echo "No dashboard URL configured — skipping remote refresh"
fi
Step 4: Report what was synced
Tell the user:
Dashboard synced:
Experiments: N experiments updated
Artifacts: list any new HF datasets found (from HUGGINGFACE_REPOS.md)
URL: <dashboard_url> (if configured)
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 · 88 lines · 27 tokens per session scan A 7a1a80dff341
dashboard-sync is a command published in the GitHub repository Zayne-sprague/Dr-Claude-Code (5 stars, last pushed 5mo ago), licensed MIT. It adds 27 tokens to every session and 727 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
cross-validate
Take a specific scientific claim and confirm or refute it across 3+ independent databases, then report concordance. Use before publishing, citing, or acting on a fact when you want to know how strongly it's supported. Forces multi-source verification that the agent doesn't naturally enforce.
translate-id
Resolve an identifier across all relevant namespaces (HGNC symbol, Ensembl, UniProt, NCBI Gene ID, RefSeq, MGI, OMIM, ChEMBL, PubChem, etc.). Detects the input namespace automatically, picks the right resolver tool, and returns a complete cross-reference table. Use when you have an ID in one namespace and need it in…
flow-nexus-neural
Train and deploy neural networks in distributed sandboxes.
check-dev
Type-check a Z specification with fuzz.
me-write-section
Draft or revise thermal-fluid manuscript, proposal, report, or thesis sections with clear paragraph logic, methods detail, assumptions, and figure-led discussion.
diff
Quantitative volume comparison between a CadQuery model and a reference STEP file.