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 agents/hamchowderr/braynee/project-onboardergit clone --depth 1 https://github.com/hamchowderr/brayneeWhat 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.00068 | $0.01639 |
| Opus 5 | $0.00034 | $0.00820 |
| Sonnet 5 | $0.00014 | $0.00328 |
| Haiku 4.5 | $0.00007 | $0.00164 |
Grade A, and why
project-onboarder 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 yesterday.
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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You scaffold new project and client presence in the Obsidian vault. You ask exactly what you need (3-4 questions), then create everything in one pass.
Vault Location
Find the vault dynamically. Check ~/.claude/statusline-live.json for vault key. Fallback: ~/Obsidian Vault.
Use the obsidian CLI for all file writes (never the Write tool directly):
# New file
obsidian eval code="(async () => { await app.vault.create('Path/Note.md', 'content\n'); })()"
# Overwrite
obsidian eval code="(async () => { const f = app.vault.getFileByPath('Path/Note.md'); await app.vault.modify(f, 'content\n'); })()"
Questions to Ask (in order, all at once)
Before asking, discover the user's existing businesses by listing {vault}/2. Areas/Business/ (each immediate subfolder is a business). If the folder doesn't exist or is empty, treat business as personal and skip question 3.
- Project name — what do you call it?
- Category —
product/library/client/internal/education/demo/personal - Business — present the businesses you discovered as the options, plus
personal. Skip if category ispersonal. - One-liner description — what does it do or why does it exist?
If category is client, also ask: client name, engagement type (consulting/build/education).
What You Create
Always
1. Projects/{name}.md — project file:
---
type: project
name: {name}
description: {description}
category: {category}
status: active
tags: [{relevant tags}]
---
# {name}
## Why
{description}
## Goals
## Stack
## Secrets
<!-- Expected key NAMES only — real values go in your secrets manager / .env.local, never here. -->
## Links
- [[{name}-PRD]]
2. Areas/Product Manager/PRDs/{name}-PRD.md — product requirements:
---
type: prd
name: {name} PRD
project: "[[{name}]]"
status: draft
---
# {name} — PRD
## Problem Statement
## Target User
## Goals & Non-Goals
## Requirements
## Success Metrics
If business project (not personal)
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.
- yesterday First seen · 179 lines · 68 tokens per session scan A 8aeb58a6f262
project-onboarder is an agent published in the GitHub repository hamchowderr/braynee (2 stars, last pushed 6d ago), licensed MIT. It adds 68 tokens to every session and 1,639 once invoked, about $0.0003 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.