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/michaeljauk/brain-starter/project-syncnpx skills add michaeljauk/brain-starter --skill project-syncgit clone --depth 1 https://github.com/michaeljauk/brain-starterWrote 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/michaeljauk/brain-starter/project-sync)<a href="https://agentmods.dev/skills/michaeljauk/brain-starter/project-sync"><img src="https://agentmods.dev/badge/skills/michaeljauk/brain-starter/project-sync.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00073 | $0.01589 |
| Opus 5 | $0.00036 | $0.00794 |
| Sonnet 5 | $0.00015 | $0.00318 |
| Haiku 4.5 | $0.00007 | $0.00159 |
Grade A, and why
project-sync 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.
How it starts
The opening of the file, as written. The whole thing — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
project-sync
On-demand AI-powered sync of a project's repo state into the brain vault. Reads live git/GitHub/Jira data, updates the project status doc, and makes targeted edits to relevant brain docs where content is clearly stale.
Trigger phrases
/project-sync [project-name]- "sync acme"
- "update project docs for [project]"
- "what's the current state of [project]"
Default project: set your own default, or require an explicit argument.
Config
Load project config from ~/brain/scripts/repos.json. Each entry has:
repo_path— local repo pathgh_repo— GitHubowner/repoforghCLIjira— (optional){ "project_key": "ACME", "site": "your-org.atlassian.net" }status_doc— AI-owned status file (always overwritten)brain_docs— list of brain notes to review and potentially update
Step-by-step workflow
1. Gather repo data
Run these commands against the project's repo_path:
# Recent commits (last 14 days)
git -C {repo_path} log --oneline --since="14 days ago" --format="%h %s (%an, %ar)"
# Active branches (excluding stale)
git -C {repo_path} branch -r --sort=-committerdate | head -20
# Current branch + status
git -C {repo_path} status --short
# Open PRs
gh pr list --repo {gh_repo} --json number,title,author,labels,createdAt,url --limit 20
# Recently merged PRs (last 7 days)
gh pr list --repo {gh_repo} --state merged --json number,title,mergedAt,url --limit 10
2. Gather Jira data (if configured)
If the project has a jira config, use acli to pull issue data:
# Recently updated issues (last 14 days)
acli jira workitem search --jql "project = {project_key} AND updated >= -14d ORDER BY updated DESC" --fields "key,summary,status,assignee,priority" --limit 30 --json
# Current sprint issues
acli jira workitem search --jql "project = {project_key} AND sprint in openSprints() ORDER BY priority ASC" --fields "key,summary,status,assignee,priority" --limit 50 --json
# Blocked / flagged issues
acli jira workitem search --jql "project = {project_key} AND status = Blocked ORDER BY priority ASC" --fields "key,summary,status,assignee,priority" --json
# Issues due this week
acli jira workitem search --jql "project = {project_key} AND duedate <= endOfWeek() AND status != Done ORDER BY duedate ASC" --fields "key,summary,status,assignee,duedate" --json
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 · 171 lines · 73 tokens per session scan A 2bb59f450a3e
project-sync is a skill published in the GitHub repository michaeljauk/brain-starter (5 stars, last pushed 7d ago), licensed MIT. It adds 73 tokens to every session and 1,589 once invoked, about $0.0004 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
context-compression
Сжатие исторического контекста контуров и проектов: поддержка meetings/README.md как краткой памяти по прошлым встречам, решениям, разворотам, открытым вопросам, устаревшим договорённостям и якорным встречам. ОБЯЗАТЕЛЬНО используй этот скилл, когда пользователь просит: «сожми историю», «сделай скользящее окно»…
new-dialog-handoff
Безопасный переход в новый диалог, когда чат стал длинным или агент прогнозирует скорое исчерпание контекстного окна. Скилл переиспользует parking и resume, фиксирует durable source of truth и готовит короткий restart-packet для свежего чата. ОБЯЗАТЕЛЬНО используй, когда пользователь говорит: «новый диалог», «перенеси…
alive-bundle
Create, manage, and graduate bundles -- the unit of focused work within a walnut.
log
Use this when a PersonalOS work session, chat outcome, personal reflection, or provided source should be persisted into the modular Daily context and any already-owned canonical files. Do NOT use for single-call processing, single-source knowledge ingestion, Gmail/WhatsApp propagation, or Lexware booking.
analyse-call
Use this when a local call transcript or meeting note should be analyzed into traceable PersonalOS context. Preserves the source, separates evidence from interpretation, updates only proven owner truth, routes confirmed commitments through task-manager, and never sends messages or triggers external actions without…
remember
Capture knowledge to your Second Brain when triggered by "remember this", "save this", or "brain dump".