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/onboard-person/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/onboard-person)<a href="https://agentmods.dev/skills/benoror/obsidianos_work/onboard-person"><img src="https://agentmods.dev/badge/skills/benoror/obsidianos_work/onboard-person/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/onboard-person"><img src="https://agentmods.dev/badge/skills/benoror/obsidianos_work/onboard-person.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.01061 |
| Opus 5.5 | $0.00018 | $0.00424 |
| Sonnet 5.5 | $0.00009 | $0.00212 |
| Haiku 4.5 | $0.00005 | $0.00106 |
Grade A, and why
onboard-person 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 1mo 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Onboard Person
Usage
/onboard-person <Name>— Create or enrichTeams/People/@<Name>.md. Pulls from available MCPs (an applicant-tracking system for hiring data, a professional-network profile source for bio)./onboard-person @<Name>— Same; bracket-less form also accepted./onboard-person <Name> --candidate— Treat as a candidate stub (lower-confidence frontmatter, parked inTeams/People/Candidates/).
Why this skill exists
When a new teammate joins, manually creating their @Name.md file means hopping between your ATS, a profile source, and the vault to copy FullName, Team, Location, Start Date, and so on. This skill consolidates the data pull and stub creation into one prompt.
It's complementary to /people-stubs: that one creates empty stubs from unresolved wikilinks; this one fills out a single stub with real metadata.
Workflow
Step 1: Check what exists
Teams/People/@<Name>.mdexists? → enrich mode (add missing properties, never overwrite existing ones)- Doesn't exist? → create mode
Step 2: Gather metadata
Try the following sources in order, accumulating what each returns. Which MCPs are available depends on your setup — examples below:
| Source | MCP / tool | Pulls |
|---|---|---|
| ATS (if MCP available, e.g. Greenhouse) | the ATS's MCP tools (when set up) | FullName, Role, Start Date, Hiring manager, Team (mapped from job → team) |
| Profile source (if MCP available, e.g. LinkedIn) | the profile MCP (when set up) | FullName, Location, Job title, Profile URL |
| Manual fallback | Prompt the user | Whatever's missing |
If neither MCP is set up yet, gracefully fall back to manual input — prompt the user for each property one at a time, defaults filled in from the wikilink display name (e.g. [[@Jane Doe]] → FullName: Jane Doe).
Step 3: Resolve Team
Use known mappings (e.g. eng membership → [[+Engineering]], design → [[+Design]], etc.). Cross-reference with Teams/+TeamName.md files via obsidian list folders path=Teams to confirm the team file exists.
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.
- 1mo ago First seen · 84 lines · 45 tokens per session scan A f71b89a81e42
onboard-person is a skill published in the GitHub repository benoror/obsidianos_work (165 stars, last pushed 4mo ago), licensed MIT. It adds 45 tokens to every session and 1,061 once invoked, about $0.0002 per session on Opus 5.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
mass-ulw
Drives dependency-ordered child work through the native workflow tool, each phase's stages defined up front in one run, with retry/amend/send recovery. Use when the user asks for mass-ulw, a DAG of tasks, or fan-out work where some tasks must wait on others.
github-triage
Read-only GitHub triage for issues AND PRs. 1 item = 1 background task (category: quick). Analyzes all open items and writes evidence-backed reports to /tmp/{datetime}/. Every claim requires a GitHub permalink as proof. NEVER takes any action on GitHub - no comments, no merges, no closes, no labels. Reports only.…
polya-plan
Phase 2 of the Pólya Heuristic Coder: Devising a Plan, Land and Expand Strategy, Vertical Tracer Bullets, Expand-Contract Pattern, Contingency Plan B, Task Sizing, and The Pause Rule (docs/plan/{slug}-plan.md).
to-plan
Phase 2 of the Pólya Heuristic Coder: Devising a Plan, Land and Expand Strategy, Vertical Tracer Bullets, Expand-Contract Pattern, Contingency Plan B, Task Sizing, and The Pause Rule (docs/plan/{slug}-plan.md).
to-prd
Optional Phase 0.5 of the Pólya Heuristic Coder: Product Requirements Document (PRD) detailing User Stories, SMART Acceptance Criteria, Personas, and Business Goals.
shopify-project-copilot
Continue a Shopify app from its last blocker, inspect local app metadata, hand off decisions, record optional feedback or report progress. Reconcile saved evidence with current files; no background service or deployment authority.