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/claudiodangelis/banco/syncgit clone --depth 1 https://github.com/claudiodangelis/bancoWrote 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/claudiodangelis/banco/sync)<a href="https://agentmods.dev/commands/claudiodangelis/banco/sync"><img src="https://agentmods.dev/badge/commands/claudiodangelis/banco/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.00000 | $0.00729 |
| Opus 5 | $0.00000 | $0.00365 |
| Sonnet 5 | $0.00000 | $0.00146 |
| Haiku 4.5 | $0.00000 | $0.00073 |
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 4d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sync
Pulls data from configured remote providers and writes it to the local filesystem.
banco sync # sync all configured providers
banco sync <name> # sync a specific provider by name or alias
banco sync <name> --module tasks # sync only the tasks module
banco sync <name> --module repos # sync only the repos module
banco sync <name> --pattern "myorg/frontend" # sync only projects matching regex
banco sync <name> --jobs 10 # clone/fetch up to 10 repos at once
--module and --pattern can be combined: banco sync github --module tasks --pattern "myorg/.*".
Sync is non-destructive: it never deletes or overwrites existing files.
Options
| Option | Description |
|---|---|
--module <tasks|repos> |
Limit sync to a single module; skips the other. Useful when you only want to fetch issues without cloning repos, or vice versa. |
--pattern <regex> |
Only sync projects whose path (owner/repo for GitHub/GitLab) matches this regex. Applied on top of the project list already defined in the provider config. Not applicable to Jira. |
--jobs <n>, -j <n> |
Number of repos to clone/fetch concurrently. Defaults to 6. Repo syncing is network-bound, so this is a small fixed value rather than something derived from CPU cores — raising it mainly risks tripping the remote's connection or rate limits. |
Sync state
After each successful sync, banco writes a timestamp to .banco/sync-state/<provider>. This
records when the last sync completed and is available for informational purposes. The state file
is only written on success, so a failed sync is retried in full on the next run.
Tasks (issues)
Syncing tasks is a two-phase process: fetch then reconcile.
Phase 1 — fetch. Only open/non-done issues are pulled from the remote. The full set of currently-open issues is always retrieved.
Phase 2 — reconcile. After writing the fetched issues, banco scans every local task file. Any task whose ID was not in the fetched set and whose local status is not already done/closed is marked done/closed — it was completed on the remote and simply disappeared from the open results.
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.
- 4d ago First seen · 62 lines · 0 tokens per session scan A ba0d31ae3a0a
sync is a command published in the GitHub repository claudiodangelis/banco (58 stars, last pushed 14d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 729 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
git
Git operations with intelligent commit messages and workflow optimization.
sc:recommend
Ultra-intelligent command recommendation engine - recommends the most suitable SuperClaude commands for any user input.
pm-arch
Scan project structure and generate Mermaid architecture diagrams + flowcharts under .pm/architecture/.
pm-done
Close a todo (TODO-xxx), sync completed.md, refresh overview.
pm-review
Review local git diff with reasoning + snippets; cross-check; dispose findings into the rules library.
pm-status
Show governance health, wizard next step, all open blocking/high todos, and pending review count. Primary daily entry.