dayze-life-context

dayze-life-context is a skill for Cursor from gohluke/dayze-mcp. It costs 39 tokens per session (440 once invoked), scanned A, original, MIT.

A connection to Dayze, a hosted service that stores personal context such as calendars, people, food, events, and photos. It can also provide information packs about notable public figures.

In plain words
What is it for?
It helps answer questions about your plans and contacts, log meals or events, manage personal records, and look up public-figure information.
Why use it?
It lets an agent retrieve or record this information through Dayze instead of guessing from chat history or storing it as ordinary conversation memory.

Skill for Cursor

Written for Cursor: shipped in a Cursor plugin.

Part of the dayze plugin — 1 skill, 2 MCP servers shipped together

Good fit It helps answer questions about your plans and contacts, log meals or events, manage personal records, and look up public-figure information.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gohluke/dayze-mcp/dayze-life-context
Install

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.

Any agent
npx skills add gohluke/dayze-mcp --skill dayze-life-context
Clone the repo
git clone --depth 1 https://github.com/gohluke/dayze-mcp

Made for: Cursor.

Or install dayze, the plugin that ships this one along with the rest of its 1 skill, 2 MCP servers.

Wrote 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.

agentmods badge for dayze-life-context

README.md
[![agentmods](https://agentmods.dev/badge/skills/gohluke/dayze-mcp/dayze-life-context/github.svg)](https://agentmods.dev/skills/gohluke/dayze-mcp/dayze-life-context)
Your own site
<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.

agentmods 80×15 button for dayze-life-context

Your own site · 80×15
<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>
Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 440 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 7d ago against content hash c62a2c39fc06, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

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.

skills/dayze-life-context/SKILL.md · 24 lines

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

  1. Signed-in user asking about their week, people, plans, or "context pack" → get_context_pack first (optional query). Do not invent a life graph from chat history.
  2. Celebrity / public figure / "how old in days" → public notable_search then notable_pack (slug). No login required; after the anonymous free tier the server may 402 (x402 USDC). Authenticated Dayze keys skip that.
  3. 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.
  4. Photos → upload_photo / get_entity_assets. CRM get_person_photos is 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.

Changes

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.

  1. 7d ago First seen · 24 lines · 39 tokens per session scan A c62a2c39fc06

Subscribe to this mod's changes

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.

Related

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.

rhein1/agoragentic-integrations · 54 tokens

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…

cyberchitta/llm-context.py · 90 tokens

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…

cdeust/Cortex · 93 tokens

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'…

cdeust/Cortex · 98 tokens

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…

cdeust/Cortex · 94 tokens

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…

cdeust/Cortex · 99 tokens