agentmods.dev

claude-code-power-config: Skill for Claude Code

.claude/skills/daily-note/SKILL.md

daily-note is a skill for Claude Code from AlexisBalayre/claude-code-power-config. It costs 21 tokens per session (991 once invoked), scanned A, original, MIT.

A helper for maintaining daily notes in Obsidian, a note-taking app, using issue-tracker and Git activity.

In plain words
What is it for?
It helps create morning plans, carry unfinished items forward, summarize work, and record status or check-ins.
Why use it?
It reduces the manual work of gathering tasks, unfinished work, and code changes into a daily record.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths.

This is AlexisBalayre/claude-code-power-config's own configuration. It tells Claude Code how to work on claude-code-power-config itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything claude-code-power-config configures →

not rated 2repo 1mo ago A scan 21 tokens original MIT
View source ↗ AlexisBalayre/claude-code-power-config
Reuse

Borrowing it

Nothing to install: this file belongs to AlexisBalayre/claude-code-power-config. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/AlexisBalayre/claude-code-power-config/main/.claude/skills/daily-note/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/AlexisBalayre/claude-code-power-config

Made for: Claude Code.

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 daily-note

README.md
[![agentmods](https://agentmods.dev/badge/skills/alexisbalayre/claude-code-power-config/daily-note/github.svg)](https://agentmods.dev/skills/alexisbalayre/claude-code-power-config/daily-note)
Your own site
<a href="https://agentmods.dev/skills/alexisbalayre/claude-code-power-config/daily-note"><img src="https://agentmods.dev/badge/skills/alexisbalayre/claude-code-power-config/daily-note/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 daily-note

Your own site · 80×15
<a href="https://agentmods.dev/skills/alexisbalayre/claude-code-power-config/daily-note"><img src="https://agentmods.dev/badge/skills/alexisbalayre/claude-code-power-config/daily-note.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 991 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 original No closer match found 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.00021 $0.00991
Opus 5.5 $0.00008 $0.00396
Sonnet 5.5 $0.00004 $0.00198
Haiku 4.5 $0.00002 $0.00099

Measured 2mo ago against content hash 785449403864, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

daily-note 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.

.claude/skills/daily-note/SKILL.md · 90 lines

How it starts

The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Daily Logbook Assistant (--plan, --summary, --status, --checkin)

You manage the user's daily Obsidian notes, synchronizing tracker issues and Git activity.

Setup: this skill reads an issue-tracker MCP server (examples use a Linear-style API) and your Obsidian vault. Fill in your own IDs and paths via .env (see .env.example) and enable the server in .claude/settings.local.json. The mcp__linear-server__* tool names are placeholders — swap them for your tracker's tools.

Configuration & Context

Read these from .env (never hardcode real account IDs or personal paths):

  • Obsidian Path: $OBSIDIAN_VAULT/$OBSIDIAN_DAILY_DIR/ (e.g., Daily Logbook/)
  • Template: $OBSIDIAN_VAULT/Templates/Daily Log.md
  • Tracker: Assignee ${TRACKER_ASSIGNEE_ID}, Team ${TRACKER_TEAM_ID}.
  • Git Author: derive from git config user.name, e.g. --author="$(git config user.name)".

Execution Modes

1. Morning Plan (--plan)

Goal: Create today's note with goals and carryover.

  1. Date Check: Get today's date (YYYY-MM-DD). If the note exists, ask before overwriting.
  2. Carryover: Read yesterday's note. Extract unchecked items from the Cache section.
  3. Tracker Sync: Fetch In Progress and To Do issues assigned to the user.
  4. Note Creation: Populate the template.
    • Focus: Highest priority issue.
    • Objectives: Top 3 issues.
    • Tasks: All fetched issues + carryover.
  5. Output: Write to $OBSIDIAN_VAULT/$OBSIDIAN_DAILY_DIR/{YYYY-MM-DD}.md. Confirm with task counts.

2. Evening Summary (--summary)

Goal: Update today's note with progress and artifacts.

  1. Read Note: Locate today's file. Stop if missing.
  2. Fetch Activity:
    • Git: git log --oneline --since="today 00:00" --author="$(git config user.name)".
    • GitHub: gh pr list --author=@me --search="created:>=YYYY-MM-DD".
    • Tracker: Identify issues marked Done today.
  3. Update Sections:
    • Tasks: Mark completed items [x].
    • Output: Insert commit hashes and PR links.
    • Cache: Move remaining [ ] tasks here for tomorrow.
    • Preserve: Do NOT overwrite manual user edits in other sections.
  4. Output: Write changes and confirm update.

Read the full file on GitHub · 90 lines

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. 2mo ago First seen · 90 lines · 21 tokens per session scan A 785449403864

Subscribe to this mod's changes

daily-note is a skill published in the GitHub repository AlexisBalayre/claude-code-power-config (2 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 991 once invoked, about $0.0001 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.

Claude CodeProductivityagentsaianthropicclaudedeveloper-tools
Related

Other skills, from other repositories

send-email

Compose and send a one-off email to a named recipient via Resend - written in the operator's voice, then sent in-run through the shared send caps with an operator audit copy.

aeonfun/aeon · 39 tokens

caveman-help

Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".

stevesolun/ctx · 56 tokens

get-started

First-run setup for the Aeon plugin. Checks the connection to the user's Aeon agent, shows what it can do, and runs one skill so the user sees it work. Use right after the plugin is installed, or when the user asks how to get started with Aeon.

aeonfun/aeon · 61 tokens

skill-factory

A workflow that examines completed session work and turns reusable patterns into Claude Code skills.

sangrokjung/claude-forge · 122 tokens

session-wrap

Use when wrapping up a session before ending. 4 parallel subagents detect doc updates, repeated patterns, learning points, and follow-ups, then a verifier deduplicates and presents choices. Triggers on /session-wrap, session wrap, session cleanup, end of session.

sangrokjung/claude-forge · 58 tokens

toolbox

Pre/post dev toolbox — named bundles of skills/agents loaded before development work and councils of experts invoked after. Run /toolbox or the toolbox.py CLI to list, activate, initialize, export, import, and validate toolboxes. Invoke at the start or end of a dev session, when setting up a new repo, or when sharing…

stevesolun/ctx · 77 tokens