Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add koolamusic/claudefiles/plugin install studioWrote 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/commands/koolamusic/claudefiles/sync)<a href="https://agentmods.dev/commands/koolamusic/claudefiles/sync"><img src="https://agentmods.dev/badge/commands/koolamusic/claudefiles/sync/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.
<a href="https://agentmods.dev/commands/koolamusic/claudefiles/sync"><img src="https://agentmods.dev/badge/commands/koolamusic/claudefiles/sync.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.03274 |
| Opus 5.5 | $0.00000 | $0.01310 |
| Sonnet 5.5 | $0.00000 | $0.00655 |
| Haiku 4.5 | $0.00000 | $0.00327 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Re-sync the current project against its studio workspace. Unlike /studio:setup, this command assumes initialization has already happened — it re-applies the managed gitignore block and validates symlinks, but never moves project state. Run after pulling studio.yaml changes from the plugin, or when the project's .gitignore has drifted.
Optional flags:
--dry-run— print every command that would run; exit 0 with no side effects (no file writes, no commits).--message <msg>— override the default commit message used when the managed gitignore block is updated. Does not change workspace-side commit message.
Memory archival (optional)
This section runs BEFORE the main step sequence below. It archives the current Claude project memory snapshot into the studio workspace. All sub-steps are gated by memory.enabled in studio.yaml — if disabled, the entire section skips silently and control flows straight to the main Steps below. Under --dry-run, every mutating sub-step (mkdir, cp, git add/commit) prints instead of executing.
Resolve WORKSPACE first (same as step 3 below): PROJECT_ROOT=$(git rev-parse --show-toplevel); read .workspacerc; expand leading ~. All sub-steps in this section assume $WORKSPACE is set.
-
Read studio.yaml memory config. Resolve the studio config path the same way the main Steps do — but for memory archival we read from the workspace-local
studio.yaml(copied there at/studio:setuptime). Run:MEMORY_ENABLED=$(yq eval '.memory.enabled // false' "${WORKSPACE}/studio.yaml")If
MEMORY_ENABLEDisfalseor the key is missing (yq returnsfalsefor a missing path thanks to the// falsedefault), print[studio] memory archival disabled; skipping.to stderr and jump to the main Steps section below. No exit code, no side effect. -
Resolve source path via PROJECT_HASH expansion. Capture the raw source template from studio.yaml and expand
${PROJECT_HASH}inline.${PROJECT_HASH}is expanded by this command, not by Claude Code's plugin loader. The two-stage sed pipeline is load-bearing — it mirrors the directory-naming convention Claude Code uses under~/.claude/projects/:RAW_SOURCE=$(yq eval '.memory.source' "${WORKSPACE}/studio.yaml") PROJECT_HASH=$(pwd | sed 's|/|-|g' | sed 's|\.|-|g') MEMORY_SOURCE="${RAW_SOURCE//\$\{PROJECT_HASH\}/$PROJECT_HASH}" # expand leading ~ to $HOME MEMORY_SOURCE="${MEMORY_SOURCE/#\~/$HOME}"If
[[ ! -d "$MEMORY_SOURCE" ]], print[studio] no memory dir at $MEMORY_SOURCE; skipping archival.to stderr and jump to the main Steps section below. No exit code, no side effect. -
Build archive target from hostname + iso. Read
memory.archive_dir(defaultmemory/archive) andmemory.path_template(default{hostname}/{iso}) from studio.yaml:archive_dir=$(yq eval '.memory.archive_dir // "memory/archive"' "${WORKSPACE}/studio.yaml") path_template=$(yq eval '.memory.path_template // "{hostname}/{iso}"' "${WORKSPACE}/studio.yaml") HOSTNAME_SHORT=$(hostname -s) ISO=$(date -u +%Y-%m-%dT%H-%M-%SZ) REL_PATH=$(echo "$path_template" | sed "s|{hostname}|$HOSTNAME_SHORT|g; s|{iso}|$ISO|g") ARCHIVE_TARGET="${WORKSPACE}/${archive_dir}/${REL_PATH}"Append-only guard. If
[[ -e "$ARCHIVE_TARGET" ]], abort with[studio] archive target already exists: $ARCHIVE_TARGET — this violates append-only; aborting.and exit 1. This should be impossible given the second-resolution iso stamp, but the check is cheap and the invariant is load-bearing. -
Create and copy. Create the target directory and copy the full memory tree:
mkdir -p "$ARCHIVE_TARGET" cp -R "$MEMORY_SOURCE/." "$ARCHIVE_TARGET/"Every file under
$MEMORY_SOURCEis preserved, includingMEMORY.mdand any nested references. -
Report. Print the archive location and file count. Use a shell fallback for the relative path (avoids GNU-only
realpath --relative-to):REL_OUT="${ARCHIVE_TARGET#$WORKSPACE/}" N=$(find "$ARCHIVE_TARGET" -type f | wc -l | tr -d ' ') echo "[studio] memory archived: $REL_OUT ($N files)"
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.
- 1mo ago First seen · 133 lines · 0 tokens per session scan A d9329c8b8f94
sync is a command published in the GitHub repository koolamusic/claudefiles (130 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,274 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
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…