A mid-session project-context refresh command. It reads project notes and recent changes, reviews decisions and tasks, and updates the stored project memory.

Use it to reconcile notes, update task status and priorities, record new learning, and check for scope creep or missed work.

It reduces the risk of losing important decisions, following outdated requirements, or drifting away from the current goal during a long coding session.

sync — Command for Claude Code by fatihkan

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.

Clone the repo

git clone --depth 1 https://github.com/fatihkan/badi

Made for: Claude Code.

Or install badi, the plugin that ships this one along with the rest of its 81 skills, 86 commands, 30 agents, 7 hooks.

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/commands/fatihkan/badi/sync.svg)](https://agentmods.dev/commands/fatihkan/badi/sync)

Your own site

<a href="https://agentmods.dev/commands/fatihkan/badi/sync"><img src="https://agentmods.dev/badge/commands/fatihkan/badi/sync.svg" alt="Measured on agentmods" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 482 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.00000	$0.00482
Opus 5	$0.00000	$0.00241
Sonnet 5	$0.00000	$0.00096
Haiku 4.5	$0.00000	$0.00048

Measured today against content hash 2c0e1169ca55, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

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

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.

.claude/commands/sync.md · 77 lines

How it starts

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

Mid-session context refresh command. Keeps context fresh and consistent during work.

Required Tools

Read (memory and context files)
Write (writing updates)
Grep (change scan)
Bash (git status)

Procedure (9 Steps)

Step 1: Read Context

Read memory.md
Read knowledge-base.md
Read the active daily note (daily-notes/DDMMYY.md)
Check the latest handoffs/ note

Step 2: Process Notes

List the decisions made this session
Identify new learnings
Note changed requirements
Record solved and newly surfaced problems

Step 3: Manage Tasks

Mark completed tasks as "done"
Add newly surfaced tasks
Re-evaluate priorities
Check dependencies

Step 4: Contextual Self-Check

Evaluate these questions as an internal check:

"Is the current work aligned with the goal?"
"Any signs of scope creep?"
"Anything skipped or postponed?"
"Am I consistent with the user's latest requests?"

Step 5: Boyd Loop Check (OODA)

Observe: What is the current state?
Orient: How do I interpret this information?
Decide: What should the next step be?
Act: What action will I propose?

Step 6: Update Memory

Add new information to memory.md
Update or remove stale information
Resolve and note any contradictions

Step 7: Review the Event Log

Scan recent changes (git log, file changes)
Warn about unexpected changes
Order important events chronologically

Step 8: Coach Insight

Offer a brief assessment:

How is the productivity flow going?
Any distraction or blocking?
Is a break recommended?

Step 9: Status Report

=== BADI SYNC ===
Time: [time]
Session Length: [estimate]
Completed: [since the last sync]
In Progress: [active work]
New Tasks: [added]
Memory State: CURRENT / WARNING
Boyd Analysis: [summary]
Coach Note: [insight]
============================

Output Format

Updated memory file
New information added to the daily note
Status report (format above)
Suggestion or warning list when needed

Read the full file on GitHub · 77 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.

today First seen · 77 lines · 0 tokens per session scan A 2c0e1169ca55

Subscribe to this mod's changes

sync is a command published in the GitHub repository fatihkan/badi (7 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 482 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-09-06.

Memory and context Project management agents ai-workflow cli developer-tools hooks

sync