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 commands/phuryn/pm-brain/ingestgit clone --depth 1 https://github.com/phuryn/pm-brainWhat 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.00000 | $0.00421 |
| Opus 5 | $0.00000 | $0.00211 |
| Sonnet 5 | $0.00000 | $0.00084 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
ingest 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 3d 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.
What it actually says
/ingest
Route a new artifact into the brain. Four shapes, one verb.
Input
A pasted transcript, a file path, a screenshot, a URL, or a free-form note. The agent infers the shape:
- interview — customer call, user research session, sales call with prospect signal
- meeting — 1:1, exec review, roadmap discussion, kickoff, retro
- market — competitor article, screenshot, tweet, changelog, analyst note
- adhoc — anything else worth capturing that doesn't fit the other three
If shape is ambiguous, ask one question. Don't guess.
Loads
knowledge/strategy.md- The matching area for the inferred shape:
knowledge/users/insights.md(interview),stakeholders/<slug>.md(meeting),knowledge/market/(market), nothing extra (adhoc) - Active
hypotheses/<slug>.mdfiles that the artifact might touch - Last 3 entries in
ingestion/<shape>/for pattern comparison
Updates
source/<shape>/<date>-<slug>.md— immutable copy of the original artifactingestion/<shape>/<date>-<slug>.md— observations tagged (observation / interpretation / hypothesis / assumption / decision)- One or more durable destinations per the cognition pipeline:
knowledge/,hypotheses/,decisions/,stakeholders/ - Maintenance log if structural (a new persona, a new competitor, a new stakeholder)
Promotion to durable layers follows the memory promotion bar in CLAUDE.md § Memory promotion. One-off observations stay in ingestion/ until they accumulate.
Surfaces
- Where the artifact landed (source, ingestion, and which durable destinations)
- 1-3 themes promoted, or "no promotion this round"
- Any contradictions with prior evidence (preserved, not resolved)
- One open question if the operator's judgment is needed
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.
- 3d ago First seen · 38 lines · 0 tokens per session scan A c18de07271f8
ingest is a command published in the GitHub repository phuryn/pm-brain (537 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 421 tokens. 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 commands, from other repositories
obsidian-ingest
Ingest a source into the vault - the vault rewrites itself around new knowledge. Every ingest updates entities, rewrites stale claims, synthesizes new concepts, and resolves contradictions.
obsidian-health
Run a vault health check - grouped by severity, detects contradictions, concept gaps, stale claims, and structural issues.
obsidian-projects
Live project status from git + local docs - infers all context from vault notes, no config required.
obsidian-retrieval-eval
Measure how well vault search finds the right note for a natural-language question - recall@k and MRR, with the concrete failures.
research
Web research with citations - Perplexity Sonar when an API key is set, free key-less sources (Wikipedia, HackerNews, arXiv, Reddit, and more) otherwise. Deep dossier with summary, facts, timeline, players, contrarian views, open questions.
obsidian-synthesize
Automatic synthesis - scans the vault for unnamed patterns and writes synthesis pages without being asked.