What is entity-people-projects-tasks?

A post-processing workflow that turns ingested notes and history into organized pages for people, projects, and open tasks. Ingesting means importing raw material into the vault for processing; a vault is the note collection being managed.

Use it after importing vault or history data to update people and project pages, task overviews, indexes, and related documentation.

It reduces duplicate records and scattered tasks by consolidating related information while keeping its source history.

entity-people-projects-tasks — Skill for Claude Code and Codex by pbee

Install

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.

Any agent

npx skills add pbeens/obsidian-agents.md --skill entity-people-projects-tasks

Clone the repo

git clone --depth 1 https://github.com/pbeens/obsidian-agents.md

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/pbeens/obsidian-agents.md/entity-people-projects-tasks/github.svg)](https://agentmods.dev/skills/pbeens/obsidian-agents.md/entity-people-projects-tasks)

Your own site

<a href="https://agentmods.dev/skills/pbeens/obsidian-agents.md/entity-people-projects-tasks"><img src="https://agentmods.dev/badge/skills/pbeens/obsidian-agents.md/entity-people-projects-tasks/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/pbeens/obsidian-agents.md/entity-people-projects-tasks"><img src="https://agentmods.dev/badge/skills/pbeens/obsidian-agents.md/entity-people-projects-tasks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,369 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00048	$0.02369
Opus 5	$0.00024	$0.01184
Sonnet 5	$0.00010	$0.00474
Haiku 4.5	$0.00005	$0.00237

Measured 10d ago against content hash 6ba674874f19, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

entity-people-projects-tasks 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.

skills/entity-people-projects-tasks/SKILL.md · 220 lines

How it starts

The opening of the file, as written. The whole thing — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Entity People, Projects & Task Consolidation

Use this skill immediately after vault-ingest, data-ingest, or history-ingest. It is a post-processing pass.

Purpose

Turn newly processed material into durable, alias-friendly People and Project pages plus consolidated task overviews, while preserving provenance and avoiding duplicates.

Invocation Examples

"Run vault-ingest on _raw/ then apply entity-people-projects-tasks"
"Process raw folder and consolidate people/projects/tasks"
"After history ingest, run people/project/task consolidation"
"entity-people-projects-tasks"

Before You Start

Run the appropriate ingest skill first (vault-ingest for _raw/, history-ingest codex for history, etc.).
Read this AGENTS.md and current tasks.md.
Check .manifest.json, people/, projects/, Bases/, and existing task overview files.

Core Order

Ingest first.
Reconcile People and Project entities.
Consolidate open tasks.
Update indexes/READMEs and log changes.

People Rules

Prefer creating or updating the page in the people/ folder.
Use root or another appropriate folder only when it clearly fits the vault's existing organization better.
Always use alias-friendly naming: clean, readable filename + rich aliases: YAML frontmatter (nicknames, short forms, spelling variations, context-specific references).
Include: short bio stub, key facts, related projects, related tasks/links.
Merge new information safely into the best existing canonical page (check filename + aliases).
Preserve provenance markers; prefer additive edits over wholesale overwrites.
Every people page must include ## Overview, ## Related Projects, and ## Related Notes, even when some sections are empty.
Every newly created or updated people page must include at least one explicit source reference in ## Related Notes.
The source reference must point to the originating note or file that caused the people page to be created.
If no related project is detected, still include the source note under ## Related Notes.
Do not leave a people page without provenance just because there is no related project.
When linking the source note, prefer an explicit path-based internal link or otherwise unambiguous source reference.
Every people page must include ## Overview, ## Related Projects, and ## Related Notes, even when some sections are empty.
Every newly created or updated people page must include at least one explicit source reference in ## Related Notes.
The source reference must point to the originating note or file that caused the people page to be created.
If no related project is detected, still include the source note under ## Related Notes.
Do not leave a people page without provenance just because there is no related project.
When linking the source note, prefer an explicit path-based internal link or otherwise unambiguous source reference.

Read the full file on GitHub · 220 lines

Changes

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 · 220 lines · 48 tokens per session scan A 6ba674874f19

Subscribe to this mod's changes

entity-people-projects-tasks is a skill published in the GitHub repository pbeens/obsidian-agents.md (20 stars, last pushed 4mo ago), licensed MIT. It adds 48 tokens to every session and 2,369 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.

Memory and context Productivity

Cortex

Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…

danielmiessler/LifeOS · 196 tokens

Migrate

Intakes external content, classifies chunks against LifeOS taxonomy, commits with provenance. Sources: .md/.txt, stdin, LifeOS dirs, CLAUDE.md/Cursor/OpenAI Custom Instructions, Obsidian/Notion/Apple Notes exports. MigrateScan classifies → routing table. MigrateApprove with…

danielmiessler/LifeOS · 158 tokens

daily-briefing

Proactive daily briefing that fires on a recurring schedule, pulls recent memory and workspace context, composes a structured summary (action items, progress, radar, next steps), and delivers it to all active channels. Enable with a time like "set up my daily briefing at 9am". Disable, reschedule, or check status at…

vellum-ai/vellum-assistant · 75 tokens

company-brain

Your team's shared, AI-ready knowledge base — people, companies, meetings, SOPs, and decisions structured so Claude can answer questions on your team's behalf. Team-scope sibling to second-brain (which is personal-scope). Seven modes — capture (drop something into the right structured dir), compile (process into wiki…

coreyhaines31/makerskills · 322 tokens

calendar

Manage calendar events via CalDAV (Google/iCloud/Nextcloud) or local ICS files. View, create, and query events.

fuyuxiang/echo-agent · 29 tokens

email-assistant

Read, search, draft, and send emails via Himalaya CLI or Python IMAP/SMTP. Requires email account configuration.