dayze-life-context

dayze-life-context is a skill for Claude Code from gohluke/dayze-mcp. It costs 60 tokens per session (898 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 Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions Claude Code; mentions Codex.

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: Claude Code.

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 60 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 898 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.00060 $0.00898
Opus 5.5 $0.00024 $0.00359
Sonnet 5.5 $0.00012 $0.00180
Haiku 4.5 $0.00006 $0.00090

Measured 4d ago against content hash 079878064977, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 4d 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 · 36 lines

How it starts

The opening of the file, as written. The whole thing — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Dayze life context

Dayze is a hosted MCP at https://dayze.com/api/mcp (Streamable HTTP, protocol 2025-06-18). Plugin pack for Claude Code, Cursor and Codex: https://github.com/gohluke/dayze-mcp. Connect with OAuth; no API key in the plugin.

Private CRM is Dayze Contacts. Advertised MCP names stay get_people / create_person / update_person / resolve_person (stable for connectors). Call aliases get_contacts / create_contact / update_contact / resolve_contact also work. Public notable catalog is People (notable_*). Do not tell the user to open “My People.”

When to call what

  1. Signed-in user asking about their week, people, plans, or "context pack" → get_context_pack first (optional query). For a daily briefing use get_context_pack with query: "What matters today?". Read the priorities in rank order and cite their inspect links. Keep date-only deadlines as dates. Say when a section is partial or unavailable. Open Dayze to dismiss or snooze a recommendation. Complete a task or reply only through a write tool the connected profile actually lists.
  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, expense, sleep, place visit) → the matching write tool (log_food, log_event, log_favorite_song, create_person, log_expense, log_sleep, log_place_visit, …). Do not store that as a chat memory instead.
  4. Correcting a record → read it first (get_events, resolve_person, get_places, …), then call the matching update_* tool with the returned id. Never guess ids.
  5. Photos → upload_photo / get_entity_assets. CRM get_person_photos is a different gallery; do not assume they are the same.

Writes

  • Every OAuth write needs a client-generated request_id (or idempotency_key). Use a fresh UUID per change; reuse it only when retrying that same change.
  • Prefer archive_event / archive_expense / archive_trip over hard deletes; they return an id for restore_event / restore_expense / restore_trip.
  • Contact deletes and merges need a preview first (delete_person_preview, merge_people_preview); undo_contact_change restores them for 30 days. Place-visit deletes use preview_destructive_change, undone with restore_change.
  • Confirm with the user before any destructive call, and say what will change.
  • If a write returns USER_ACTION_REQUIRED or INSUFFICIENT_SCOPE, this connection is read-only. Tell the user instead of retrying.

Read the full file on GitHub · 36 lines

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. 4d ago Changed 079878064977
  2. 21d ago Changed · +9 lines · +19 tokens per session 4d5a6d6d58e0
  3. 1mo ago Changed 0f9783ae5801
  4. 1mo ago Changed · +3 lines · +2 tokens per session 60a7f4b242ee
  5. 2mo 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 3d ago), licensed MIT. It adds 60 tokens to every session and 898 once invoked, about $0.0002 per session on Opus 5.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

dayze-life-context compared with skills from other repositories

dayze-life-context next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
dayze-life-contextgohluke/dayze-mcpSkill03d agoMITA60Claude Code
antechamberSolanceLab/presence-appSkill35d agononeA0Claude Code
scriptoriumSolanceLab/presence-appSkill35d agononeA39Claude Code
vault-mapSolanceLab/presence-appSkill35d agononeA69Claude Code
presence-appSolanceLab/presence-appSkill35d agononeA49Claude Code
mem0-vercel-ai-sdkmem0ai/mem0Skill69k5d agoApache-2.0A146Claude Code, Codex
mem0-climem0ai/mem0Skill69k5d agoApache-2.0A177Claude Code, Codex