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/last-1on1/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/last-1on1)<a href="https://agentmods.dev/skills/benoror/obsidianos_work/last-1on1"><img src="https://agentmods.dev/badge/skills/benoror/obsidianos_work/last-1on1/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/benoror/obsidianos_work/last-1on1"><img src="https://agentmods.dev/badge/skills/benoror/obsidianos_work/last-1on1.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00050 | $0.00865 |
| Opus 5 | $0.00025 | $0.00432 |
| Sonnet 5 | $0.00010 | $0.00173 |
| Haiku 4.5 | $0.00005 | $0.00086 |
Grade A, and why
last-1on1 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Last 1:1
Usage
/last-1on1— Show last 1:1 date per person across all of your 1:1s. Default flag threshold: 2 weeks (anything older highlighted)./last-1on1 <weeks>— Custom flag threshold (e.g./last-1on1 3)./last-1on1 @Name— Just for one person.
Why this skill exists
Direct-report 1:1s and peer syncs are easy to skip when calendars get busy. This skill surfaces the gap — "haven't talked to [[@Alex Kim]] in 3 weeks" — so the next scheduling round prioritizes them.
Workflow
Step 1: Pull the source data
Query obsidian base:query path=Meetings.base view=OneOnOnes format=json. Returns every meeting under Meetings/One-on-ones/ and Meetings/Tech Syncs/ with file.ctime and Participants columns.
Step 2: Aggregate by person
For each meeting, extract the participant name(s) from Participants (skipping [[@Me]] and team links like [[+Engineering]]). For each participant, track the most recent file.ctime.
Edge case: the file ctime is when the note was created, which is usually the day of the meeting — but for older imported notes it may be the import date. If a meeting filename has a YYYY-MM-DD suffix, prefer that over file.ctime.
Step 3: Present sorted table
Sort by last_date ASC (oldest first — most overdue at the top):
| # | Person | Last 1:1 | Days ago | Status |
|---|--------|----------|----------|--------|
| 1 | [[@Jane Doe]] | 2026-02-05 | 117 | 🔴 overdue |
| 2 | [[@John Smith]] | 2026-04-09 | 54 | 🔴 overdue |
| 3 | [[@Alex Kim]] | 2026-05-06 | 27 | 🟡 due soon |
| 4 | [[@Sam Rivera]] | 2026-05-26 | 7 | ✅ recent |
| 5 | [[@Pat Lee]] | 2026-05-27 | 6 | ✅ recent |
- 🔴 overdue:
days_ago > threshold * 2(default >28 days) - 🟡 due soon:
threshold < days_ago <= threshold * 2 - ✅ recent:
days_ago <= threshold
Step 4: Offer next action
After the table, suggest:
- "Schedule a 1:1 with the top-3 overdue: [[@Jane Doe]], [[@John Smith]], [[@Alex Kim]]?"
- For each, optionally
/meeting <Name> x Meto create a stub for the upcoming meeting.
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 · 64 lines · 50 tokens per session scan A 417519e58f6b
last-1on1 is a skill published in the GitHub repository benoror/obsidianos_work (165 stars, last pushed 3mo ago), licensed MIT. It adds 50 tokens to every session and 865 once invoked, about $0.0003 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.