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 borisvu/obsidian-vault-cowork-plugins --skill daily-reportgit clone --depth 1 https://github.com/borisvu/obsidian-vault-cowork-pluginsWrote 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/borisvu/obsidian-vault-cowork-plugins/daily-report)<a href="https://agentmods.dev/skills/borisvu/obsidian-vault-cowork-plugins/daily-report"><img src="https://agentmods.dev/badge/skills/borisvu/obsidian-vault-cowork-plugins/daily-report/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/borisvu/obsidian-vault-cowork-plugins/daily-report"><img src="https://agentmods.dev/badge/skills/borisvu/obsidian-vault-cowork-plugins/daily-report.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.00043 | $0.02153 |
| Opus 5 | $0.00022 | $0.01077 |
| Sonnet 5 | $0.00009 | $0.00431 |
| Haiku 4.5 | $0.00004 | $0.00215 |
Grade A, and why
daily-report 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 11d 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 — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Daily Report Skill
Generate clean daily reports from Work Diary entries. This skill is organized into numbered sections that commands reference directly.
Section 1: Core Concepts
Work Diary Location
Work Diary/
├── YYYY/
│ └── MM/
│ └── YYYY-MM-DD.md # Daily notes
└── gggg/
└── MM/
└── gggg-[W]ww.md # Weekly notes (ISO week)
Daily Note Template
---
tags:
- Daily_Report
---
# Goals
- [ ]
# Worked on today
-
# Achievements
-
# To do on the next working day
-
# Free notes
Work Week
Sunday through Thursday (Israel).
| Today | Last work day | Next work day |
|---|---|---|
| Sunday | Thursday | Monday |
| Monday | Sunday | Tuesday |
| Tuesday | Monday | Wednesday |
| Wednesday | Tuesday | Thursday |
| Thursday | Wednesday | Sunday |
| Friday | Thursday | Sunday |
| Saturday | Thursday | Sunday |
Section 2: Time Awareness
Before any date operations, use
~~timeMCP to get the current date, time, and day of week. This is the source of truth. NEVER guess or calculate dates manually.
Section 3: Date Range Resolution
- No argument: Last work day → today
since YYYY-MM-DD: Given date → today- Skip Friday and Saturday when iterating
Section 4: Section Extraction
From each daily note, extract content from these sections (per the template in Section 1):
| Section | Purpose |
|---|---|
# Goals |
What was planned (checkbox items) |
# Worked on today |
What was actually done |
# Achievements |
Notable completions |
# To do on the next working day |
Carry-forward items |
# Free notes |
Additional context |
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.
- 11d ago First seen · 306 lines · 43 tokens per session scan A 51dad48bfcc4
daily-report is a skill published in the GitHub repository borisvu/obsidian-vault-cowork-plugins (4 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 43 tokens to every session and 2,153 once invoked, about $0.0002 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
things-mac
Manage Things 3 via the things CLI on macOS (add/update projects+todos via URL scheme; read/search/list from the local Things database). Use when a user asks Otto to add a task to Things, list inbox/today/upcoming, search tasks, or inspect projects/areas/tags.
gsd-ns-manage
Route to the appropriate management skill based on the user's intent. gsd-config (settings + advanced + integrations + profile) and gsd-workspace (new + list + remove) are post-#2790 consolidated entries.
slack-tools
Slack workspace management and automation specialist.
triage-inbox
Triage academic email and calendar (Gmail / Google Calendar via the session's MCP) into a prioritized digest plus a referee-obligations tracker — classifying referee requests, R&R and editor correspondence, co-author threads, seminar and conference invites, and grant/admin deadlines, and proposing a human-gated action…
ceo-setup
One-time onboarding for the executive/manager commitment workflow — delegation-heavy, meeting prep, decision capture, morning and evening digests. Creates a commitments project and installs two dashboard widgets. After successful setup this skill is excluded from selection until the marker file is deleted.
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…