diary-study-plan

diary-study-plan is a skill for Claude Code from Infrasity-Labs/dev-gtm-claude-skills. It costs 36 tokens per session (266 once invoked), scanned A, a copy of diary-study-plan, MIT.

A plan for a diary study, a research method where participants record their experiences, actions, or feelings over days or weeks in their normal setting. It covers prompts, participants, timing, check-ins, and analysis.

In plain words
What is it for?
Use it to plan participant criteria, daily or event-based prompts, text/photo/video entries, check-ins, onboarding, analysis, and ways to handle dropouts.
Why use it?
It helps researchers understand behaviour over time instead of relying on a single interview or observation. A structured plan also reduces missed entries and makes the results easier to compare.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Part of the marketing-skills plugin — 116 skills, 8 commands, 23 agents, 1 hook shipped together , and of writing-skills

Good fit Use it to plan participant criteria, daily or event-based prompts, text/photo/video entries, check-ins, onboarding, analysis, and ways to handle dropouts.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/infrasity-labs/dev-gtm-claude-skills/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 Infrasity-Labs/dev-gtm-claude-skills --skill diary-study-plan
Clone the repo
git clone --depth 1 https://github.com/Infrasity-Labs/dev-gtm-claude-skills

Made for: Claude Code.

Or install marketing-skills, the plugin that ships this one along with the rest of its 116 skills, 8 commands, 23 agents, 1 hook.

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/infrasity-labs/dev-gtm-claude-skills/diary-study-plan/github.svg)](https://agentmods.dev/skills/infrasity-labs/dev-gtm-claude-skills/diary-study-plan)
Your own site
<a href="https://agentmods.dev/skills/infrasity-labs/dev-gtm-claude-skills/diary-study-plan"><img src="https://agentmods.dev/badge/skills/infrasity-labs/dev-gtm-claude-skills/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/infrasity-labs/dev-gtm-claude-skills/diary-study-plan"><img src="https://agentmods.dev/badge/skills/infrasity-labs/dev-gtm-claude-skills/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 8d ago against content hash c58924c2ce22, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, 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 8d 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.

.claude/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. 8d 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 Infrasity-Labs/dev-gtm-claude-skills (124 stars, last pushed 2mo 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

geo-audit

Full website GEO+SEO audit with parallel subagent delegation. Orchestrates a comprehensive Generative Engine Optimization audit across AI citability, platform analysis, technical infrastructure, content quality, and schema markup. Produces a composite GEO Score (0-100) with prioritized action plan.

techhorizonlabs/thl-open · 60 tokens

geo

GEO-first SEO analysis tool. Optimizes websites for AI-powered search engines (ChatGPT, Claude, Perplexity, Gemini, Google AI Overviews) while maintaining traditional SEO foundations. Performs full GEO audits, citability scoring, AI crawler analysis, llms.txt generation, brand mention scanning, platform-specific…

techhorizonlabs/thl-open · 139 tokens

geo-brand-mentions

Brand mention and authority scanner for AI visibility. Analyzes brand presence across platforms that AI models rely on for entity recognition and citation decisions. Produces a Brand Authority Score (0-100) with platform-specific recommendations.

techhorizonlabs/thl-open · 49 tokens

geo-llmstxt

Analyzes and generates llms.txt files -- the emerging standard for helping AI systems understand website structure and content. Can validate existing llms.txt files or generate new ones from scratch by crawling the site.

techhorizonlabs/thl-open · 46 tokens

agent-readiness-scan

Use when a client audit, GEO/AI-visibility snapshot, or remediation re-scan needs the Cloudflare agent-readiness score from isitagentready.com — e.g. Theo client audits, "is the site agent-ready", markdown negotiation / MCP / llms.txt / Content-Signal checks, or tracking score deltas after Tier 0/1 fixes.

techhorizonlabs/thl-open · 79 tokens

found-by-ai

Measure whether AI engines actually recommend a business when buyers ask. Runs the free live scan at areyoufoundbyai.com (no auth, 60s), reads the verdict and the rivals AI names instead, hands back the fix plan, and wires monitored sites into a fix-and-re-measure loop over MCP.

techhorizonlabs/thl-open · 67 tokens