diary-study-plan

diary-study-plan is a skill for Claude Code from realmpastai-web/claude-design-suite. It costs 36 tokens per session (266 once invoked), scanned A, a copy of diary-study-plan, MIT.

A diary study plan for recording people’s behavior and experiences in their everyday setting over several weeks. A diary study asks participants to submit written, spoken, photo, or video entries in response to prompts.

In plain words
What is it for?
Use it to define the study duration, participants, prompts, capture methods, check-ins, and analysis framework. It is suited to understanding behavior over time and in natural contexts.
Why use it?
It helps reveal patterns that may not appear in a single interview or test session. It also plans for onboarding, check-ins, participant drop-out, and analysis.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Part of the design-research plugin — 10 skills, 4 commands shipped together

Good fit Use it to define the study duration, participants, prompts, capture methods, check-ins, and analysis framework. It is suited to understanding behavior over time and in natural contexts.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/realmpastai-web/claude-design-suite/diary-study-plan
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 realmpastai-web/claude-design-suite --skill diary-study-plan
Clone the repo
git clone --depth 1 https://github.com/realmpastai-web/claude-design-suite

Made for: Claude Code.

Or install design-research, the plugin that ships this one along with the rest of its 10 skills, 4 commands.

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 diary-study-plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/realmpastai-web/claude-design-suite/diary-study-plan/github.svg)](https://agentmods.dev/skills/realmpastai-web/claude-design-suite/diary-study-plan)
Your own site
<a href="https://agentmods.dev/skills/realmpastai-web/claude-design-suite/diary-study-plan"><img src="https://agentmods.dev/badge/skills/realmpastai-web/claude-design-suite/diary-study-plan/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 diary-study-plan

Your own site · 80×15
<a href="https://agentmods.dev/skills/realmpastai-web/claude-design-suite/diary-study-plan"><img src="https://agentmods.dev/badge/skills/realmpastai-web/claude-design-suite/diary-study-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 266 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 86% copy Near-identical to another mod 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.00036 $0.00266
Opus 5 $0.00018 $0.00133
Sonnet 5 $0.00007 $0.00053
Haiku 4.5 $0.00004 $0.00027

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

Security

Grade A, and why

diary-study-plan 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 10d 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.

Origin

This is a copy

86% identical to diary-study-plan — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugins/design-research/skills/diary-study-plan/SKILL.md · 27 lines

What it actually says

Diary Study Plan

Design a longitudinal diary study to capture user behavior in context over time.

Context

You are a UX researcher designing a diary study for $ARGUMENTS.

Instructions

  1. Define research goals: What longitudinal behaviors or experiences are you studying?
  2. Design the study:
    • Duration: Recommended length (typically 1-4 weeks)
    • Participants: 8-15 participants, screening criteria, compensation plan
    • Entry prompts: Daily or event-triggered prompts (mix of structured and open-ended)
    • Capture methods: Photo, video, text, voice — what to ask participants to document
    • Check-in schedule: Mid-study interviews or pulse surveys
    • Onboarding: Participant briefing, practice entries, tool setup
  3. Create an analysis framework: How to code, theme, and synthesize entries across participants.
  4. Plan for attrition: Strategies to keep participants engaged throughout the study.
  5. Present as a ready-to-execute research plan.
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. 10d ago First seen · 27 lines · 36 tokens per session scan A c58924c2ce22

Subscribe to this mod's changes

diary-study-plan is a skill published in the GitHub repository realmpastai-web/claude-design-suite (2 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 266 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to diary-study-plan, differing in 2 lines, and is treated as a copy.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens