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 commands/dynokostya/just-works/git-syncgit clone --depth 1 https://github.com/Dynokostya/just-worksWrote 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/dynokostya/just-works/git-sync)<a href="https://agentmods.dev/commands/dynokostya/just-works/git-sync"><img src="https://agentmods.dev/badge/commands/dynokostya/just-works/git-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.00015 | $0.00662 |
| Opus 5 | $0.00008 | $0.00331 |
| Sonnet 5 | $0.00003 | $0.00132 |
| Haiku 4.5 | $0.00002 | $0.00066 |
Grade A, and why
git-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.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Sync
Switch all repositories (root and submodules) to the default branch and pull latest changes.
Phase 1: Detect Repositories
Run via Bash:
git rev-parse --show-toplevel
This confirms you're inside a git repository and gives the root path.
Then check for submodules:
git submodule status 2>/dev/null
If the command produces output, submodules are present. Parse each submodule path from the output (second column). If it produces no output or errors, there are no submodules — proceed with the root repo only.
Announce to the user:
Repositories found:
- <root path> (root)
- <submodule path> (submodule)
- ...
Phase 2: Detect Default Branch
For each repository (root first, then each submodule), detect the default branch. Run from within that repo's directory:
git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's|refs/remotes/origin/||'
If that fails (the ref may not exist), fall back to:
git remote show origin 2>/dev/null | grep 'HEAD branch' | sed 's/.*: //'
If both fail, check whether main or master exists locally:
git branch --list main master
Pick whichever exists. If both exist, prefer main. If neither exists, report the error for that repo and skip it.
Phase 3: Sync
For each repository, run these commands in sequence. Stop processing a repo if any command fails and report the error.
- Fetch all remotes:
git fetch --all --prune
- Switch to the default branch:
git checkout <default-branch>
If checkout fails due to uncommitted changes, report this to the user and skip the repo. Do not stash, reset, or discard changes.
- Pull latest:
git pull
Phase 4: Report
After processing all repositories, present a summary:
Sync complete:
✓ <root path> — switched to main, pulled (up to date / X commits pulled)
✓ <submodule path> — switched to master, pulled (up to date / X commits pulled)
✗ <submodule path> — uncommitted changes, skipped
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 · 102 lines · 15 tokens per session scan A 6e50e75029ff
git-sync is a command published in the GitHub repository Dynokostya/just-works (14 stars, last pushed today), licensed Apache-2.0. It adds 15 tokens to every session and 662 once invoked, about $0.0001 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-09-04.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.