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 skills add gohluke/dayze-mcp --skill dayze-life-contextgit clone --depth 1 https://github.com/gohluke/dayze-mcpWrote 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/skills/gohluke/dayze-mcp/dayze-life-context)<a href="https://agentmods.dev/skills/gohluke/dayze-mcp/dayze-life-context"><img src="https://agentmods.dev/badge/skills/gohluke/dayze-mcp/dayze-life-context/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/gohluke/dayze-mcp/dayze-life-context"><img src="https://agentmods.dev/badge/skills/gohluke/dayze-mcp/dayze-life-context.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00039 | $0.00440 |
| Opus 5 | $0.00019 | $0.00220 |
| Sonnet 5 | $0.00008 | $0.00088 |
| Haiku 4.5 | $0.00004 | $0.00044 |
Grade A, and why
dayze-life-context 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 7d 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.
What it actually says
Dayze life context
Dayze is a hosted MCP at https://dayze.com/api/mcp (Streamable HTTP, protocol 2025-06-18, server v1.14.0). Same tools/list for ChatGPT, Claude, Cursor, and Gemini. Cursor plugin pack: https://github.com/gohluke/dayze-mcp — connect with OAuth; no API key in the plugin.
When to call what
- Signed-in user asking about their week, people, plans, or "context pack" →
get_context_packfirst (optionalquery). Do not invent a life graph from chat history. - Celebrity / public figure / "how old in days" → public
notable_searchthennotable_pack(slug). No login required; after the anonymous free tier the server may 402 (x402 USDC). Authenticated Dayze keys skip that. - User is logging something they did (meal, event, song, person) → the matching write tool (
log_food,log_event,log_favorite_song,create_person, …). Do not store that as a chat memory instead. - Photos →
upload_photo/get_entity_assets. CRMget_person_photosis a different gallery; do not assume they are the same.
Auth
OAuth is discovered from RFC 9728. Request scopes openid email mcp context offline_access. Private tools need context. Share tokens are read-only (get_context_pack, get_life_graph only). Never ask the user to paste an API key into chat.
Aliases
Some tools document aliases (date for event_date, query for q). Prefer the required schema field names (event_date, q, query on search) so strict clients do not drop the call.
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.
- 7d ago First seen · 24 lines · 39 tokens per session scan A c62a2c39fc06
dayze-life-context is a skill published in the GitHub repository gohluke/dayze-mcp (0 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 440 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-09-04.
Other skills, from other repositories
agoragentic-buzz-signed-workspace-evidence
Convert exported Block Buzz / Nostr workspace events into bounded Agoragentic evidence. Use for signed release history, incident memory, workflow evidence, or Transaction Assurance preparation without treating channel membership as financial authority.
lc-curate-context
Decide which files a task actually needs, record that as a reusable llm-context rule, verify it against the codebase - including the files your selection references but leaves out - and pack it for your own context, a chat, or a sub-agent you dispatch. Load when choosing what code to put in front of a model, packing…
cortex-automate
Set up automation — prospective memory triggers, neuro-symbolic rules, and CLAUDE.md sync. Use when the user says 'remind me when', 'trigger when', 'create a rule', 'auto-remember', 'sync to CLAUDE.md', 'push insights', 'set up trigger', 'when I open this file', 'when this keyword appears', or when you want to…
cortex-profile
View and manage your cognitive profile — how you think, work patterns, blind spots, and cross-domain connections. Use when the user says 'show my profile', 'how do I work', 'what are my patterns', 'cognitive style', 'blind spots', 'methodology', or at the start of a session to load context. Also use 'rebuild profile'…
cortex-recall
Search and retrieve memories from Cortex persistent memory. Use when the user asks 'what did we decide about X', 'do you remember', 'what was the fix for', 'find that thing about', 'search memories', 'what do we know about', 'have we seen this before', or when you need context about past decisions, patterns, bugs, or…
cortex-remember-global
Store a global memory that is visible across all projects. Use when the user shares architecture rules, coding conventions, infrastructure facts, security policies, team agreements, or any knowledge that applies beyond a single project. Triggers on 'remember this everywhere', 'this applies to all projects', 'global…