Borrowing it
Nothing to install: this file belongs to theshadow27/mcp-cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/theshadow27/mcp-cli/main/.claude/skills/diary/SKILL.mdgit clone --depth 1 https://github.com/theshadow27/mcp-cliWrote 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/theshadow27/mcp-cli/diary)<a href="https://agentmods.dev/skills/theshadow27/mcp-cli/diary"><img src="https://agentmods.dev/badge/skills/theshadow27/mcp-cli/diary/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/theshadow27/mcp-cli/diary"><img src="https://agentmods.dev/badge/skills/theshadow27/mcp-cli/diary.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.00087 | $0.00610 |
| Opus 5.5 | $0.00035 | $0.00244 |
| Sonnet 5.5 | $0.00017 | $0.00122 |
| Haiku 4.5 | $0.00009 | $0.00061 |
Grade A, and why
diary 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Diary: Session Transcript Analysis
Generate diary entries from Claude Code session JSONL transcripts stored in
~/.claude/projects/<project-key>/.
How it works
- Run the extraction script to produce per-date text extracts
- Spawn one Sonnet agent per date (in parallel, foreground) to analyze and write entries
- Multiple entries per day are supported (YYYYMMDD.md, YYYYMMDD.1.md, YYYYMMDD.2.md, etc.)
Step 1: Run the extraction script
bun run .claude/skills/diary/extract-sessions.ts
This outputs a JSON manifest to stdout listing which dates need diary entries and where the extract files are. Parse it.
Step 2: Spawn analysis agents
For each date in the manifest, spawn a Sonnet agent (NOT background — foreground, but
all in parallel in a single message) with this prompt template. Use diaryFilename
from the manifest for the output path — it handles the .N.md suffix automatically.
You are analyzing Claude Code session transcripts from the mcp-cli project.
Read the file {extract_path} which contains extracted text from sessions on {date}.
Also read {diary_dir}/20260310.md for the format/style reference.
Write a diary entry to {diary_dir}/{diaryFilename} following this format:
- # {formatted_date} — Title (short thematic title)
- ## What was done (PRs, features, fixes — with issue/PR numbers where visible)
- ## What worked well
- ## What didn't work
- ## Patterns established (if any new ones emerged)
Extract specific issue/PR numbers, technical details, and concrete learnings.
Be specific about what code was changed. Keep it concise but specific — like
good engineering notes, not a summary report.
Step 3: Report
After all agents complete, list the diary entries created with their titles.
Notes
- The extraction script derives the project key from the current working directory
- Sessions with fewer than 5 user messages are filtered out (worker sessions, quick chats)
- Top 6 sessions per date by size are included
- Text is capped at ~25K chars per session to fit in agent context
- XML system tags (system-reminder, local-command-caveat, etc.) are stripped
- Only user and assistant text blocks are extracted (no tool_use/tool_result)
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 66 lines · 87 tokens per session scan A e45b7933b0f6
diary is a skill published in the GitHub repository theshadow27/mcp-cli (2 stars, last pushed 3d ago), licensed MIT. It adds 87 tokens to every session and 610 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
agentmail
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by your inbox assignment.
Cortex
LifeOS memory, prior-session recall, and learning capture. USE WHEN capture this learning, document this learning, what did we learn recently, recent learnings, cortex, knowledge, knowledge base, search knowledge, what do we know about, archive, harvest, knowledge status, develop note, add to knowledge, add a people…
rowboat-spaces
How to work as a member of Rowboat Spaces, the team chat where people and agents work together. Load it once per session, before acting on any request that reaches you from Rowboat; it covers your setup, mentions and hand-offs, the tools, and files.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.