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.
curl -O https://raw.githubusercontent.com/AlexisBalayre/claude-code-power-config/main/.claude/skills/daily-note/SKILL.mdgit clone --depth 1 https://github.com/AlexisBalayre/claude-code-power-configWrote 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/alexisbalayre/claude-code-power-config/daily-note)<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.
<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>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.00021 | $0.00991 |
| Opus 5 | $0.00010 | $0.00495 |
| Sonnet 5 | $0.00004 | $0.00198 |
| Haiku 4.5 | $0.00002 | $0.00099 |
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 10d 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 — 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. Themcp__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.
- Date Check: Get today's date (
YYYY-MM-DD). If the note exists, ask before overwriting. - Carryover: Read yesterday's note. Extract unchecked items from the Cache section.
- Tracker Sync: Fetch
In ProgressandTo Doissues assigned to the user. - Note Creation: Populate the template.
- Focus: Highest priority issue.
- Objectives: Top 3 issues.
- Tasks: All fetched issues + carryover.
- 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.
- Read Note: Locate today's file. Stop if missing.
- 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
Donetoday.
- Git:
- 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.
- Tasks: Mark completed items
- Output: Write changes and confirm update.
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.
- 10d ago First seen · 90 lines · 21 tokens per session scan A 785449403864
daily-note is a skill published in the GitHub repository AlexisBalayre/claude-code-power-config (2 stars, last pushed 29d ago), licensed MIT. It adds 21 tokens to every session and 991 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-31.
Other skills, from other repositories
skill-factory
A workflow that examines completed session work and turns reusable patterns into Claude Code skills.
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.
relay
Session relay — compresses what's been done so far (writes a one-liner for /compact) and generates a "next task" prompt (a baton) for the user to hand off. Use on requests like "relay / hand off / next session / continue after compact / baton / handoff / clean up context and continue next task." Does not run /compact…
strategic-compact
Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.
session-save
Save the current session state (decisions, modified files, current status, and next steps) to a handoff file for later resume.
handoff-create
Generate a structured handoff document from the current session. Captures scope, relevant files with line numbers, key discoveries, work completed, current status, next steps, and code snippets. Use before ending a session or handing work to another agent.