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/followup-todos/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/followup-todos)<a href="https://agentmods.dev/skills/benoror/obsidianos_work/followup-todos"><img src="https://agentmods.dev/badge/skills/benoror/obsidianos_work/followup-todos/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/followup-todos"><img src="https://agentmods.dev/badge/skills/benoror/obsidianos_work/followup-todos.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.00045 | $0.01884 |
| Opus 5 | $0.00023 | $0.00942 |
| Sonnet 5 | $0.00009 | $0.00377 |
| Haiku 4.5 | $0.00005 | $0.00188 |
Grade A, and why
followup-todos 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Follow-up Todos
Usage
/followup-todos <path>— Extract and propose follow-ups from a specific meeting note./followup-todos(no args) — Run /note-status pending --step=todos to show meetings missing follow-up extraction. The user picks one (or more) to process.
Output format (mandatory)
- Never insert Obsidian Tasks / checkbox lines: no
- [ ],- [x],- [-], or any- [?]pattern. - Never append Tasks-plugin inline metadata on inserted lines: no
📅,🛫,⏳, or other parsed task tokens. (Optional priority emoji at the very end as plain text — e.g.🔼— is fine if it reads naturally in prose.) - Always insert plain list items:
- Description…Wikilinks ([[@Name]],[[+Team]]) and bold are allowed.
Prerequisites
The meeting file should ideally have cached AI transcripts (from /cache-notes). If not cached, suggest running /cache-notes <path> first. However, the skill also works on notes with only manual content.
Optional context
For classification (owner, urgency, dates in the proposal step), you may still use people-resolver and obsidian-tasks as reference — but do not copy Tasks checkbox or date-token syntax into the note.
Workflow
Step 1: Read the meeting note and gather context
See vault-context for vault discovery conventions.
Read the entire file. Also read Tracker.md to cross-reference Jira tickets and current task status — this helps:
- Set priority: A ticket already marked
🔺in the Tracker should keep that priority (as trailing emoji in the bullet text if you include one). - Avoid duplicates: If a follow-up already exists in the Tracker for the same Jira ticket, flag it in the proposal table (Step 3) rather than creating a duplicate line in the note.
- Add context: If the meeting references a Jira ticket ID (e.g.
PROJ-1234), pull its current status and assignee from the Tracker.
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 · 138 lines · 45 tokens per session scan A 7aa1eda0d92a
followup-todos is a skill published in the GitHub repository benoror/obsidianos_work (165 stars, last pushed 3mo ago), licensed MIT. It adds 45 tokens to every session and 1,884 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.