agentspec: Command for Claude Code

.claude/commands/core/sync-context.md

sync-context is a command for Claude Code from luanmorenommaciel/agentspec. It costs 18 tokens per session (1,782 once invoked), scanned A, original, MIT.

A command that examines a codebase and updates CLAUDE.md, a file that gives an AI coding assistant project-specific instructions. It records current structure, conventions, and architecture while preserving manual edits.

In plain words
What is it for?
It helps refresh project guidance, update a specific section, or preview proposed changes without saving them.
Why use it?
It reduces the work of keeping the assistant's project context accurate as the code changes.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths; mentions CLAUDE.md.

This is luanmorenommaciel/agentspec's own configuration. It tells Claude Code how to work on agentspec itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agentspec configures →

Reuse

Borrowing it

Nothing to install: this file belongs to luanmorenommaciel/agentspec. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/luanmorenommaciel/agentspec/main/.claude/commands/core/sync-context.md
Clone the repo
git clone --depth 1 https://github.com/luanmorenommaciel/agentspec

Made for: Claude Code.

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.

agentmods badge for sync-context

README.md
[![agentmods](https://agentmods.dev/badge/commands/luanmorenommaciel/agentspec/sync-context/github.svg)](https://agentmods.dev/commands/luanmorenommaciel/agentspec/sync-context)
Your own site
<a href="https://agentmods.dev/commands/luanmorenommaciel/agentspec/sync-context"><img src="https://agentmods.dev/badge/commands/luanmorenommaciel/agentspec/sync-context/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.

agentmods 80×15 button for sync-context

Your own site · 80×15
<a href="https://agentmods.dev/commands/luanmorenommaciel/agentspec/sync-context"><img src="https://agentmods.dev/badge/commands/luanmorenommaciel/agentspec/sync-context.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,782 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00018 $0.01782
Opus 5.5 $0.00007 $0.00713
Sonnet 5.5 $0.00004 $0.00356
Haiku 4.5 $0.00002 $0.00178

Measured 1mo ago against content hash 7010ff14bd68, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

sync-context 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 1mo 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.

.claude/commands/core/sync-context.md · 348 lines

How it starts

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

Sync Context Command

Analyzes codebase and intelligently updates CLAUDE.md with current project context.

Usage

/sync-context                    # Full analysis and update
/sync-context --section agents   # Update specific section
/sync-context --dry-run          # Preview changes without saving

What It Does

  1. Analyzes current codebase structure
  2. Extracts patterns, conventions, and architecture
  3. Merges with existing CLAUDE.md content
  4. Preserves manual customizations
  5. Updates sections that need refresh

Analysis Process

Step 1: Scan Codebase Structure

# Discover project structure
Glob("**/*.py")              # Python files
Glob("**/*.ts")              # TypeScript files
Glob("**/package.json")      # Node projects
Glob("**/pyproject.toml")    # Python projects
Glob("**/Dockerfile")        # Container configs
Glob("**/*.tf")              # Terraform

Step 2: Extract Patterns

# Code patterns
Grep("@dataclass")           # Dataclass usage
Grep("class.*Parser")        # Parser patterns
Grep("def test_")            # Test patterns
Grep("async def")            # Async patterns

# Architecture patterns
Grep("from src")             # Import structure
Grep("@router")              # API patterns
Grep("@lambda_handler")      # Lambda patterns

Step 3: Analyze Agents

# List available agents
Glob(".claude/agents/**/*.md")

# Categorize by folder
- workflow/       → SDD pipeline agents (brainstorm, define, design, build, ship, iterate)
- architect/      → System design (schema, pipeline, lakehouse, genai, planner)
- cloud/          → AWS, GCP, CI/CD, deployment agents
- platform/       → Microsoft Fabric specialists
- python/         → Code review, clean, document, prompt engineering
- test/           → Testing, data quality, data contracts
- data-engineering/ → Spark, dbt, Airflow, Lakeflow, streaming, SQL
- dev/            → Codebase explorer, meeting analyst, prompt crafter

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

  1. 1mo ago First seen · 348 lines · 18 tokens per session scan A 7010ff14bd68

Subscribe to this mod's changes

sync-context is a command published in the GitHub repository luanmorenommaciel/agentspec (256 stars, last pushed 3d ago), licensed MIT. It adds 18 tokens to every session and 1,782 once invoked, about $0.0001 per session on Opus 5.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-09-01.