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/bybren-llc/a-safe-pulse/syncgit clone --depth 1 https://github.com/bybren-llc/a-safe-pulseWrote 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/bybren-llc/a-safe-pulse/sync)<a href="https://agentmods.dev/commands/bybren-llc/a-safe-pulse/sync"><img src="https://agentmods.dev/badge/commands/bybren-llc/a-safe-pulse/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.00000 | $0.00654 |
| Opus 5 | $0.00000 | $0.00327 |
| Sonnet 5 | $0.00000 | $0.00131 |
| Haiku 4.5 | $0.00000 | $0.00065 |
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 yesterday.
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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description = "Full local development sync after git pull"
prompt = """
Local Sync Command
Perform complete local development environment sync after pulling from dev branch. This ensures dependencies, database, and validation are all up-to-date.
Workflow
1. Git Branch Cleanup (Best Practice)
Check current branch and switch to dev if needed:
!{git branch --show-current}
If on feature branch:
- Check for uncommitted changes
- If clean, switch to dev:
git checkout dev - If dirty, offer to stash:
git stash && git checkout dev
2. Git Pull
Pull latest changes from origin/dev:
!{git pull origin dev}
If pull fails due to uncommitted changes:
- Stash changes:
git stash - Pull again
- Reapply stash:
git stash pop
3. Branch Cleanup (Git Best Practice)
After pulling latest dev, clean up merged branches:
!{git branch --merged dev | grep -v "^\\*" | grep -v "dev" | grep -v "master"}
Offer to delete merged feature branches.
Prune remote tracking branches:
!{git fetch --prune origin}
4. Smart Change Detection
Detect what changed to determine necessary steps:
!{git diff HEAD@{1} HEAD -- package.json package-lock.json 2>/dev/null | head -5}
Decision Logic:
- If deps changed → Run npm install
- If schema changed → Check migration files
- If both empty → Fast path: Jump to Docker check
5. Install Dependencies (Conditional)
Only run if package.json or package-lock.json changed:
!{npm install 2>&1 || echo "Install completed"}
6. Database Migration Check (Conditional)
Only run if migration files changed:
!{ls -la src/db/migrations/ 2>&1 || echo "Migration check completed"}
Note: Raw SQL migrations in src/db/migrations/ run automatically on application startup.
7. Validation (Optional)
Ask user: "Run full validation (npm test && npm run build)?"
If user chooses Yes:
!{npm test && npm run build 2>&1 || echo "Validation completed"}
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.
- yesterday First seen · 121 lines · 0 tokens per session scan A 0c78dab274b5
sync is a command published in the GitHub repository bybren-llc/a-safe-pulse (9 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 654 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-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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.