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/fill-participants/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/fill-participants)<a href="https://agentmods.dev/skills/benoror/obsidianos_work/fill-participants"><img src="https://agentmods.dev/badge/skills/benoror/obsidianos_work/fill-participants/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/fill-participants"><img src="https://agentmods.dev/badge/skills/benoror/obsidianos_work/fill-participants.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 67 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00025 | $0.01546 |
| Opus 5 | $0.00013 | $0.00773 |
| Sonnet 5 | $0.00005 | $0.00309 |
| Haiku 4.5 | $0.00003 | $0.00155 |
Grade A, and why
fill-participants 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fill Participants
Usage
/fill-participants all— Scan all meetings, find those missing Participants, resolve and fill them./fill-participants <path>— Fill participants for a specific meeting note (relative to workspace root, e.g.Meetings/Engineering/Some Meeting.md).
Frontmatter Conventions
See people-resolver for wikilink format and name matching rules.
Participants live in YAML frontmatter as either:
# Single participant
Participants: "[[@Jane Doe]]"
# Multiple participants
Participants:
- "[[@Jane Doe]]"
- "[[@Alex Kim]]"
# Team-wide meetings
Participants: "[[+Engineering]]"
Workflow
Step 1: Identify targets
Mode A (all):
Run /note-status pending --step=participants to discover notes missing Participants:, present them, and let the user select which to process.
Mode B (specific file):
- Read the specified file.
- Check if Participants already exists in frontmatter. If so, inform user and stop (or ask if they want to override).
Step 2: Gather participant info for each target
For each meeting missing Participants, determine attendees using the resolution priority defined in people-resolver. In summary:
- External transcript sources — Use the source linked in
Notes:frontmatter:- Google Docs: Extract document ID from
Notes:, fetch content withgws(gws docs documents getorgws drive files exportto plain text — see google-workspace-cli); Gemini summaries name participants explicitly. - Otter.ai: Use otter-fetch when an Otter URL is in
Notes:(user pastes JSON; runparse_otter.jsor parse inline).
- Google Docs: Extract document ID from
- File name —
X x Ypatterns. - File content — Existing
[[@Name]]references. - Folder conventions — e.g.
Meetings/Engineering/Scrum/→[[+Engineering]]. - Similar meetings — Recurring meeting with same name, different date.
- Tracker.md — Jira ticket assignees for disambiguation.
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 · 132 lines · 25 tokens per session scan A d6e55f1f0166
fill-participants is a skill published in the GitHub repository benoror/obsidianos_work (165 stars, last pushed 3mo ago), licensed MIT. It adds 25 tokens to every session and 1,546 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-30.
Other skills, from other repositories
plannotator-compound
Analyze a user's Plannotator plan archive to extract denial patterns, feedback taxonomy, evolution over time, and actionable prompt improvements — then produce a polished HTML dashboard report. Falls back to Claude Code ExitPlanMode denial reasons when Plannotator data is unavailable.
plannotator
Reference for using the Plannotator CLI: plan review, code review, annotating files, URLs, folders, and running local apps, annotating the last assistant message, browsing archived plan decisions, and exporting or sharing Guided Reviews. Invoke when asked to use Plannotator for anything not covered by a more specific…
plannotator-visual-explainer
Generate self-contained HTML visualizations with Plannotator theming. Use for implementation plans, PR explainers, architecture diagrams, data tables, slide decks, and any visual explanation of technical concepts. Plans and PR explainers follow Plannotator's prescriptive approach; all other visual content delegates to…
plannotator-annotate
Open Plannotator's annotation UI for a file, folder, or URL, then address the returned annotations.
plannotator-last
Open Plannotator on the latest rendered assistant message and use the returned annotations to revise that message or continue.
ulw-research
Runs maximum-saturation research with a cooperating team, claim-graph gating, and a cited, QA'd deliverable. Use when the user explicitly asks for research or a deep investigation, including any 'ulw' research wording.