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/today-hookgit 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/today-hook)<a href="https://agentmods.dev/commands/datacore-one/datacore/today-hook"><img src="https://agentmods.dev/badge/commands/datacore-one/datacore/today-hook.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.00334 |
| Opus 5 | $0.00003 | $0.00167 |
| Sonnet 5 | $0.00001 | $0.00067 |
| Haiku 4.5 | $0.00001 | $0.00033 |
Grade A, and why
today-hook 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.
What it actually says
Analytics Hook: /today Integration
Command Context
When to Reference Analytics Module
Always reference when:
- /today command is invoked (automatic hook)
- User asks about website traffic, visitors, or analytics
Quick Reference
| Question | Answer |
|---|---|
| What format? | Markdown table with per-project metrics |
| What period? | Last 24 hours vs previous 24 hours |
| What projects? | Datacore, PLUR, Datafund |
| What if API fails? | Show "Analytics unavailable" and continue |
Trigger
Called by /today command when analytics module is installed.
Section to Generate
Web Analytics (PostHog)
Run the daily metrics script:
python3 .datacore/modules/analytics/lib/posthog_daily.py
Include the output directly in the briefing. The script outputs a markdown table with visitors, pageviews, sessions, and day-over-day change for each project.
Conditions
- If the script fails or returns an error, show:
Analytics: unavailable (API error) - If all metrics are 0, note it may be due to recent project migration
- Do not block the rest of /today if analytics fails
Tone
Data-first. Just the numbers, no commentary unless there's a notable spike or drop (>50% change).
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 · 56 lines · 6 tokens per session scan A 00d5d70b34fe
today-hook 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 334 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).