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.
npx skills add faizkhairi/claude-code-blueprint --skill save-diarygit clone --depth 1 https://github.com/faizkhairi/claude-code-blueprintWrote 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/faizkhairi/claude-code-blueprint/save-diary)<a href="https://agentmods.dev/skills/faizkhairi/claude-code-blueprint/save-diary"><img src="https://agentmods.dev/badge/skills/faizkhairi/claude-code-blueprint/save-diary.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 3 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00057 | $0.00865 |
| Opus 5 | $0.00028 | $0.00432 |
| Sonnet 5 | $0.00011 | $0.00173 |
| Haiku 4.5 | $0.00006 | $0.00086 |
Grade A, and why
save-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 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.
How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prerequisite check (run first): if ./memory/diary/current/ does not exist OR ~/.claude/.memory-disabled marker file is present, this skill is a no-op. Output: "Memory persistence is disabled. Run ./setup.sh and choose to enable memory if you want diary entries to be saved."
Dev Diary: Session Documentation Skill
Today's story takes shape.
Activation
When this skill activates, output: "Dev Diary: documenting today's session."
Context Guard
| Context | Status |
|---|---|
| User says "save diary" / "write diary" / "diary entry" | ACTIVE, full diary write |
| End of significant session | ACTIVE, auto-document |
| User says "review diary" | ACTIVE, read recent entries |
| Mid-conversation (no save request) | DORMANT, no diary action |
Protocol
Step 1: Monthly Archive Check
- Scan
./memory/diary/current/for files from previous months - For each file where month != current month:
- Create
./memory/diary/archived/YYYY-MM/folder if not exists - Move the file from
current/toarchived/YYYY-MM/
- Create
- Continue with diary write
Step 2: Find or Create Today's File
- Check if
./memory/diary/current/YYYY-MM-DD.mdexists - If exists: use it (will append new entry)
- If not: create new file with header:
# YYYY-MM-DD, Session N: Brief Description
Step 3: Compose and Append Diary Entry
- Get current date via bash:
date +"%B %d, %Y"or PowerShellGet-Date -Format "MMMM dd, yyyy" - Analyze current session for key content
- Write structured entry using our actual diary format:
- Title:
# YYYY-MM-DD, Session N: Brief Description - What Happened: Concise summary of the session context and goals
- Fixes Applied / Key Changes: Specific technical work done (commits, code changes)
- Key Insight: Lessons learned or important observations
- Pending / Next Steps: What's left to do
- Title:
- Session numbering: Read the existing file first. Find the highest
Session Nnumber in today's entries and increment by 1. If this is the first entry of the day, check the previous day's file for the last session number and continue from there. If no previous entries exist, start at Session 1. - APPEND to today's file (never overwrite existing content)
- Multiple entries per day are separated by
---
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.
- 8d ago First seen · 84 lines · 57 tokens per session scan A 573b8ee3f954
save-diary is a skill published in the GitHub repository faizkhairi/claude-code-blueprint (70 stars, last pushed 27d ago), licensed MIT. It adds 57 tokens to every session and 865 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
nft-standards
Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.
postgresql-table-design
Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.
istio-traffic-management
Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
workflow-orchestration-patterns
Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running processes, distributed transactions, or microservice orchestration.
microservices-patterns
Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.