Borrowing it
Nothing to install: this file belongs to benoror/obsidianos_work. 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/benoror/obsidianos_work/main/.agents/skills/recap/SKILL.mdgit clone --depth 1 https://github.com/benoror/obsidianos_workWrote 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/benoror/obsidianos_work/recap)<a href="https://agentmods.dev/skills/benoror/obsidianos_work/recap"><img src="https://agentmods.dev/badge/skills/benoror/obsidianos_work/recap.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.00033 | $0.02142 |
| Opus 5 | $0.00016 | $0.01071 |
| Sonnet 5 | $0.00007 | $0.00428 |
| Haiku 4.5 | $0.00003 | $0.00214 |
Grade A, and why
recap 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 7d 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Recap
Usage
/recap— Recap the current week (Monday through today)./recap [dates]— Recap a specific date range.
Date Filtering
See date-filter for the full syntax and date parsing rules.
Default (omitted): Monday through today (current week).
Data Sources
The recap pulls from all available sources. Unavailable sources are skipped gracefully with a note in the output.
| Source | Tool | Status | What to gather |
|---|---|---|---|
| Gmail | gws (Gmail API) |
✅ When gws is authenticated |
Emails sent/received in the date range |
| Vault notes | QMD (CLI or MCP) | ✅ When QMD index exists | Meeting notes, daily notes, any .md file dated within range |
| Google Calendar | gws (Calendar API) |
✅ When gws is authenticated |
Events in the date range (for context) |
| Slack | slack MCP (optional) |
⏳ Pending setup | Channel messages, DMs, threads |
| Jira | atlassian MCP (optional) |
⏳ Pending setup | Issues assigned/updated/commented, sprint activity |
| Confluence | atlassian MCP (optional) |
⏳ Pending setup | Pages created/updated, comments |
When a source is unavailable (gws / QMD / optional MCP not installed, not authenticated, or errors), log it under a ### ⏳ Unavailable Sources section in the output and proceed with the remaining sources.
Workflow
Step 1: Parse date range
Resolve the [dates] argument into a concrete start_date and end_date (inclusive, YYYY-MM-DD format). Default: Monday of the current week through today.
Step 2: Gather data
Run the following in parallel where possible:
2a. Vault notes (QMD + Tracker)
See vault-context for the full convention.
Gather vault context for the date range: meeting notes from Meetings/**/* (any naming format) and Tracker.md (sprint/task status). Use QMD for discovery, always include the Tracker, and extract titles, participants, discussion points, existing todos, and AI summaries from each matched file.
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.
- 7d ago First seen · 194 lines · 33 tokens per session scan A b2d87b2e4543
recap is a skill published in the GitHub repository benoror/obsidianos_work (166 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 2,142 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-30.
Other skills, from other repositories
give-me-tips
Explains any senpi tip in depth, including Tip: lines in the TUI. Use when the user asks about a tip, what a tipped feature does, or which tips they can see.
general
Handle everyday conversation, answer questions, manage files, take notes, run scripts, and maintain persistent memory across sessions. Use when the user asks a general question, requests file operations, wants to brainstorm ideas, needs to-do tracking, asks you to remember something, or requests skill search and…
message-push
Send proactive messages to IM groups or individual users via the gateway Send API. Use when the user says to send, post, notify, forward, or tell someone a message on Feishu, Slack, Telegram, Discord, DingTalk, or WeCom.
task-manager
Creates and manages scheduled tasks, cron jobs, recurring reminders, and timers via the Task HTTP API. Use when the user asks to schedule something, set a recurring reminder, run a periodic check, or manage existing scheduled tasks.
meeting
Meeting notes assistant — organizes transcripts into structured minutes, extracts action items, and tracks attendee decisions. Use when the user asks to summarize a meeting, take meeting notes, write up minutes, create a meeting recap, list attendees, or extract action items from a call.
project-memory-keeper
Analyzes the last session to log progress, extract lessons learned, and save them to the project memory instructions.