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 skills add dhaupin/vant --skill vant-skill-syncgit clone --depth 1 https://github.com/dhaupin/vantWrote 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/skills/dhaupin/vant/vant-skill-sync)<a href="https://agentmods.dev/skills/dhaupin/vant/vant-skill-sync"><img src="https://agentmods.dev/badge/skills/dhaupin/vant/vant-skill-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/skills/dhaupin/vant/vant-skill-sync"><img src="https://agentmods.dev/badge/skills/dhaupin/vant/vant-skill-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.00008 | $0.00317 |
| Opus 5.5 | $0.00003 | $0.00127 |
| Sonnet 5.5 | $0.00002 | $0.00063 |
| Haiku 4.5 | $0.00001 | $0.00032 |
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.
What it actually says
Sync
Pull and push your brain.
When To Use
- Start of session (pull)
- End of session (push)
- Manual sync
How To Sync
Pull
# Get latest brain
vant sync pull
Push
# Save your changes
vant sync push
Both
# Pull then push
vant sync
What Happens
| Action | What |
|---|---|
| Pull | Get remote changes |
| Push | Send local changes |
| Sync | Do both |
Conflicts
When you and another agent changed the same thing:
## Conflict
### [FILE]
- Yours: [your change]
- Remote: [their change]
### Resolution
- [KEEP_YOURS/KEEP_THEIRS/MERGE]
Output
## Sync
### Changes
- [n] files changed
### Conflicts
- [n] files
### Pushed
- [YES/NO]
Tips
- Sync at start - get context
- Sync at end - save progress
- Sync before merge - avoid conflicts
Role: Syncer
Input: Direction (pull/push/sync)
Output: Synced brain
Keep in sync.
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 · 106 lines · 8 tokens per session scan A 5f9419327d45
sync is a skill published in the GitHub repository dhaupin/vant (11 stars, last pushed 2d ago), licensed MIT. It adds 8 tokens to every session and 317 once invoked, about $0.0000 per session on Opus 5.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-08-31.
Other skills, from other repositories
list-learned-actions
Explicit Codex workflow: List persisted reusable actions, UI skeletons, and legacy feedback memories before composing device primitives.
pr-writing-review
Extract and analyze writing improvements from GitHub PR review comments. Use when asked to show review feedback, style changes, or editorial improvements from a GitHub pull request URL. Handles both explicit suggestions and plain text feedback. Produces structured output comparing original phrasing with reviewer…
session-investigator
Investigate fast-agent session and history files to diagnose issues. Use when a session ended unexpectedly, when debugging tool loops, when correlating sub-agent traces with main sessions, or when analyzing conversation flow and timing. Covers session.json metadata, history JSON format, message structure, tool…
claw-memory-management
Workspace memory management guide: memory layers, writing rules, entry format, and maintenance. Use when writing, updating, or maintaining memory files (memory/YYYY-MM-DD.md and MEMORY.md).
hive.context-preservation
Proactively extract critical values from tool results into working notes before automatic context pruning destroys them.
hive.note-taking
Maintain a free-form scratchpad of decisions, extracted values, and open questions so context pruning doesn't lose anything you still need.