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 Dqz00116/skill-lib --skill daily-loggit clone --depth 1 https://github.com/Dqz00116/skill-libWrote 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/dqz00116/skill-lib/daily-log)<a href="https://agentmods.dev/skills/dqz00116/skill-lib/daily-log"><img src="https://agentmods.dev/badge/skills/dqz00116/skill-lib/daily-log.svg" alt="Measured on agentmods" 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.00018 | $0.01861 |
| Opus 5 | $0.00009 | $0.00931 |
| Sonnet 5 | $0.00004 | $0.00372 |
| Haiku 4.5 | $0.00002 | $0.00186 |
Grade A, and why
daily-log 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 — 279 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Daily Log Skill
Overview
Generate comprehensive daily operation logs to track work, decisions, and lessons learned.
When to Use
Use this skill at the end of a work session or day to:
- Record completed tasks and their outcomes
- Track token usage and time spent
- Document key decisions and their rationale
- Capture lessons learned and mistakes
- Maintain continuity across sessions
Log Format Templates
Template A: Full Detail (Legacy)
Use for: Important milestones, detailed project records See: FULL_TEMPLATE
Template B: Attention-Driven (Recommended)
Use for: Daily work logging, quick review See below ⬇️
Attention-Driven Log Format (v1.1)
# YYYY-MM-DD Operation Log
## 📅 Session Overview
- **Date**: YYYY-MM-DD
- **Work Period**: HH:MM - HH:MM (X hours X minutes)
- **Core Outcomes**: [One-sentence summary of the day's most important output]
- **Key Decisions**: [X]
- **Lessons Learned**: [X]
- **Token Consumption**: ~XX,XXX
---
## ⏱️ Time Distribution
| Time Slot | Task | Duration | Attention Weight |
|-----------|------|----------|-----------------|
| HH:MM-HH:MM | [Task 1] | X min | 9/10 |
| HH:MM-HH:MM | [Task 2] | X min | 7/10 |
| ... | ... | ... | ... |
**Time Analysis**:
- High-attention task time: X% (mainly XX:XX-XX:XX)
- Interruptions/switches: X
- Peak efficiency period: XX:XX-XX:XX
---
## 🎯 High-Attention Tasks (Weight 8-10)
### [Task Name] (Weight: X/10, Time Slot: HH:MM-HH:MM, Duration: X min)
**One-sentence Summary**: [Core outcome or decision]
**Key Details**:
- [Specific data/numbers]
- [File paths/names]
- [Decision rationale]
- [Verification results]
**Lessons Learned** (if applicable):
- [Key takeaways]
---
## 📋 Medium-Attention Tasks (Weight 5-7)
| Task | Weight | Time Slot | Key Outcome |
|------|--------|-----------|-------------|
| [Task name] | 7/10 | HH:MM-HH:MM | [One-sentence description] |
| [Task name] | 6/10 | HH:MM-HH:MM | [One-sentence description] |
---
## 📝 Low-Attention Tasks (Weight 0-4)
- [HH:MM-HH:MM] [Task name] - [Status]
- [HH:MM-HH:MM] [Task name] - [Status]
---
## 📊 Today's Statistics
| Item | Value |
|------|-------|
| High-attention tasks | X |
| Medium-attention tasks | X |
| Low-attention tasks | X |
| Code files created | X |
| Code files modified | X |
| Skill created/updated | X |
| Token consumption | ~XX,XXX |
| Git commits | X |
---
## 💡 Today's Biggest Lesson
**One-sentence Summary**: [Core lesson]
**Background**: [What happened]
**Root Cause**: [Why it happened]
**Improvement Measures**: [How to improve]
---
## 🔗 Key File Locations
### High-Value Outputs
- `path/to/key/file1` - [One-sentence description]
- `path/to/key/file2` - [One-sentence description]
---
*Log generated at: YYYY-MM-DD HH:MM*
*Attention score: High[X] Medium[X] Low[X]*
What ships with it
2 files 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.
- 8d ago First seen · 279 lines · 18 tokens per session scan A df9b7bd5b3a1
daily-log is a skill published in the GitHub repository Dqz00116/skill-lib (22 stars, last pushed 3mo ago), licensed MIT. It adds 18 tokens to every session and 1,861 once invoked, about $0.0001 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
anyr
Use when reading, searching, creating, or updating Anytype documents (objects, spaces, types, properties, files, chats) from the command line with the configured anyr CLI, including JSON output patterns for scripting.
meeting-notes
Paste raw meeting notes and get a clean summary with key decisions and action items.
any-mcp
Use when an agent needs to read, search, create, edit, organize, upload, or chat with Anytype through the bounded any-mcp server. Covers safe tool selection, exact identifier chaining, optional toolsets, common PKM workflows, and the narrow anyr fallbacks for chat subscriptions and rich chat blocks.
anytype-setup
Install anyr and configure desktop or headless Anytype access. Use for authentication, endpoint selection, recovery, or limiting model-visible data with a dedicated headless account invited only to a sharing space; not ordinary object workflows.
saga-orchestration
Implement saga patterns for distributed transactions and cross-aggregate workflows. Use this skill when implementing distributed transactions across microservices where 2PC is unavailable, designing compensating actions for failed order workflows that span inventory, payment, and shipping services, building…
meeting-efficiency
Agenda design, time boxing, decision capture, async alternatives, and productive facilitation.