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.
git clone --depth 1 https://github.com/gonzalezpazmonica/saviaWrote 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/gonzalezpazmonica/savia/backlog-sync)<a href="https://agentmods.dev/commands/gonzalezpazmonica/savia/backlog-sync"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/savia/backlog-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.1 | $0.00022 | $0.00381 |
| Opus 5 | $0.00011 | $0.00191 |
| Sonnet 5 | $0.00004 | $0.00076 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
backlog-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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- backlog-sync — 100% identical, 0 lines differ
What it actually says
/backlog-sync
Synchronize local markdown backlog with external PM tools.
Providers
| Provider | Adapter | Requirements |
|---|---|---|
| azure-devops | sync-adapters/azure-devops-adapter.sh | AZURE_DEVOPS_ORG_URL + PAT |
| jira | sync-adapters/jira-adapter.sh | JIRA_BASE_URL + email + token |
| github | sync-adapters/github-issues-adapter.sh | gh CLI + --repo |
Actions
- pull: Download items from external tool, merge into local backlog
- push: Upload local PBIs to external tool (creates new, updates existing)
- diff: Show differences without applying changes
Conflict Policy
- Both changed: show diff, ask PM to decide
- Only local changed: push
- Only remote changed: pull
- NEVER auto-resolve state, estimation, or assignment conflicts
Steps
- Detect provider from project _config.yaml or --provider flag
- Validate credentials and connectivity
- Execute requested action via adapter script
- Log sync operation to output/.sync-log.jsonl
- Show summary with counts
Output
Sync: local ↔ azure-devops (project-name)
Created: 2 | Updated: 3 | Conflicts: 0 | Skipped: 1
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.
- 2d ago First seen · 50 lines · 22 tokens per session scan A 83113c787be8
backlog-sync is a command published in the GitHub repository gonzalezpazmonica/savia (50 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 381 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-06.
Other commands, from other repositories
wtfp:contribute
Guide a bounded WTF-P contribution from branch creation through a reviewable change request.
pr-summary
PR status summary — list open PRs, filter bots, group by ticket ID.
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
sync
Synchronizes your local swarm state with the latest GitHub repository state, updating task statuses and detecting changes.
weekly-summary
Generate weekly work summary from git activity.
next
Suggest the most likely next workflow action based on current context.