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/shdennlin/agent-plugins/syncgit clone --depth 1 https://github.com/shdennlin/agent-pluginsWhat 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.00012 | $0.00401 |
| Opus 5 | $0.00006 | $0.00200 |
| Sonnet 5 | $0.00002 | $0.00080 |
| Haiku 4.5 | $0.00001 | $0.00040 |
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.
What it actually says
Git Sync Command
Pull superproject and sync all submodules to their latest tracking branches.
Arguments
Parse the following from $ARGUMENTS:
--helpor-h- Show usage information and exit
Instructions
Step 1: Parse Arguments
From $ARGUMENTS, extract:
- help: if
--helpor-his present, show the usage information below and stop. Do NOT delegate to the agent.
Help Output
If --help or -h is present, display this and stop:
Usage: /git-workflow:sync [options]
Pull superproject and sync all submodules to latest tracking branches.
Only works in superprojects with submodules.
Options:
-h, --help Show this help message
Examples:
/git-workflow:sync Sync all submodules
Step 2: Validate Submodules Exist
git submodule status 2>/dev/null
If output is empty or the command fails, display this error and stop — do NOT delegate:
Error: No submodules found in the current repository.
This command only works in superprojects with submodules.
Step 3: Delegate to Agent
Launch the sync-agent agent:
Task tool:
- subagent_type: "sync-agent"
- description: "Sync submodules to latest"
- prompt: |
Sync the superproject and all submodules to their latest upstream state.
- Working directory: <current directory>
Examples
# Sync all submodules to latest
/git-workflow: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.
- yesterday First seen · 77 lines · 12 tokens per session scan A 37ebe04b8b26
sync is a command published in the GitHub repository shdennlin/agent-plugins (2 stars, last pushed 7d ago), licensed MIT. It adds 12 tokens to every session and 401 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-08-31.
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.