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/nicepkg/vsync/create-prgit clone --depth 1 https://github.com/nicepkg/vsyncWhat 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.00009 | $0.01207 |
| Opus 5 | $0.00005 | $0.00603 |
| Sonnet 5 | $0.00002 | $0.00241 |
| Haiku 4.5 | $0.00001 | $0.00121 |
Grade A, and why
create-pr 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.
How it starts
The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Pull Request (Semantic-release Friendly)
Create a GitHub Pull Request that works with semantic-release. This repo defaults to Squash and merge, so the PR title becomes the release commit. Therefore the PR title MUST follow Conventional Commits exactly:
<type>(<scope>): <subject>
Hard rules (must pass CI):
- Subject must be lowercase
- Subject must NOT end with a period
- Header length must be <= 100 characters
- Scope is optional, but if used must be one of:
website,docs,deps,cli
Context
- Current branch: !
git branch --show-current - Base branch: main
- Git status: !
git status --short - Changed files: !
git diff --name-only origin/main - Diff stat: !
git diff --stat origin/main - Recent commits on branch: !
git log origin/main..HEAD --oneline
Prerequisites
-
Ensure
ghCLI is available and authenticated:gh auth status -
Ensure all changes are committed and branch is pushed:
git status git push -u origin HEAD
PR Title Format (Angular Convention)
IMPORTANT: PR title MUST follow Angular/Conventional Commit format because squash uses it as the release commit.
<type>(<scope>): <subject>
Types
| Type | Description |
|---|---|
feat |
A new feature |
fix |
A bug fix |
docs |
Documentation only changes |
style |
Changes that do not affect the meaning of the code |
refactor |
A code change that neither fixes a bug nor adds a feature |
perf |
A code change that improves performance |
test |
Adding missing tests or correcting existing tests |
build |
Changes that affect the build system or external dependencies |
ci |
Changes to CI configuration files and scripts |
chore |
Other changes that don't modify src or test files |
revert |
Reverts a previous commit |
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 · 177 lines · 9 tokens per session scan A 940fff4f3745
create-pr is a command published in the GitHub repository nicepkg/vsync (57 stars, last pushed 7mo ago), licensed MIT. It adds 9 tokens to every session and 1,207 once invoked, about $0.0000 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-08-30.
Other commands, from other repositories
init-project
Configure the baseline for this specific project. Invokes the scout skill, then claude-automation-recommender, populates .claude/project.json, pre-creates lazy directories, re-renders swarm-worker.md from its template with any stack-specific skills appended, appends a §16 addendum to docs/init/seed.md, runs…
sql_schema
Command "sql_schema" from agentis-tools/ctx, covering ctx sql — public schema (v1), stability contract, views, v1.symbols — one row per symbol and v1.edges — one row per relationship.
coograph-review
Review the changes in scope for spec compliance, convention violations, logic bugs, and architectural issues. You review — you do not author. Never edit files.
coograph-verify
Verify that the described work is complete and correct. Provide evidence for every claim. You verify — you do not implement or fix style.
hotspots
Rank files and symbols by churn x complexity to find refactoring hotspots.
approve-direction
Record human approval of a workflow's direction (the intake + its acceptance criteria + the CO-A evidence). The Direction Approval Guard hook blocks Claude from ever writing approval tokens; this command is the only sanctioned path. Must be user-invoked. Replaces the retired /approve-spec gate (D3/CO-E gate-collapse)…