Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/nweii/agent-stuff/people-notesnpx skills add nweii/agent-stuff --skill people-notesgit clone --depth 1 https://github.com/nweii/agent-stuffWhat 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 | $0.00036 | $0.01519 |
| Opus 5 | $0.00018 | $0.00759 |
| Sonnet 5 | $0.00007 | $0.00304 |
| Haiku 4.5 | $0.00004 | $0.00152 |
Grade A, and why
people-notes 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 2d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
People notes
Prepare task-specific context from person notes and their linked records. Create or maintain a note only when the task calls for a vault change.
1. Choose the branch
Read the vault's AGENTS.md, then choose one branch from the user's task:
- Use — prepare context for work involving a person. This is the read-only default.
- Create — make a canonical person note when the user asks for one or the agreed vault task requires it.
- Maintain — reconcile an existing person note with newer evidence or requested corrections.
Link cleanup supports create and maintain; it is not a separate branch. A passing reference does not authorize note creation.
This step is complete when one branch is selected and the permitted read/write scope is clear.
2. Resolve the person
Search 04-Entities/ case-insensitively by canonical title and aliases. Treat body mentions and linked records as identity clues; a canonical note exists only when its title or aliases resolve the person.
Use relationship, organization, location, and source context to distinguish name variants or collisions. When two people share a full name, use a stable title qualifier such as Jordan Lee (Design) and display links such as [[Jordan Lee (Design)|Jordan Lee]].
This step is complete when one canonical note is identified, absence is confirmed, or unresolved candidates are reported.
3. Gather evidence
Start with the current conversation, the person note, and the records surfaced by ![[Related.base#Person]]. Read the recent records relevant to the task rather than dumping every backlink.
Reach beyond the vault only when the task needs more context or a freshness check. Granola meetings, Gmail threads, and verified public profiles are optional evidence sources. Continue with available evidence and report unavailable sources.
Track what each source establishes, its date, and any uncertainty. Treat Nathan's uncertainty as data; qualify or omit claims rather than resolving them by inference.
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.
- 2d ago First seen · 120 lines · 36 tokens per session scan A 576b4e16ee46
people-notes is a skill published in the GitHub repository nweii/agent-stuff (8 stars, last pushed 14d ago), licensed MIT. It adds 36 tokens to every session and 1,519 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-31.
Other skills, from other repositories
hr-onboarding
A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".
lark-im
飞书即时通讯：收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片（Interactive Card）、监听卡片按钮回调（card.action.trigger）。当用户需要发消息、查看或搜索聊天记录、下载聊天中的文件、查看群成员、搜索群、创建群聊或话题群、管理标记数据、管理 Feed 置顶（添加/移除/查询置顶会话）、管理标签数据、处理卡片回调时使用。.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
reflect
Review recent work, find repeated workflow patterns, and suggest reusable skills, agents, commands, config changes, or playbooks. Use when the user asks to learn from past sessions, improve recurring workflows, or identify what should be turned into reusable agent instructions.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.
organize-threads
猫猫辅助整理未分类 thread，分析标题和元数据，建议合适的标签。 Use when: 用户说"帮我整理"、"分类 thread"、点击整理按钮。 Not for: 删除/编辑标签本身。 Output: 按 thread 的标签建议列表。.