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/bravew/trove/shipgit clone --depth 1 https://github.com/bravew/troveWhat 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.01108 |
| Opus 5 | $0.00005 | $0.00554 |
| Sonnet 5 | $0.00002 | $0.00222 |
| Haiku 4.5 | $0.00001 | $0.00111 |
Grade A, and why
ship 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship: Commit → Push → PR
Context
- Branch: !
git branch --show-current - Status: !
git status --short - Staged: !
git diff --staged --stat
Optional PR title override: $ARGUMENTS
Steps
- Commit — Analyze staged changes and create atomic commit with conventional message
- Push — Push to remote with upstream tracking
- PR — Create PR with comprehensive description
Commit message follows conventional commits format. NEVER mention Claude Code or Anthropic.
PR Description Best Practices:
- Clear, concise summary of changes
- Explain motivation and context
- List key technical changes
- Include test plan with project-appropriate validation commands
- Note any breaking changes or migrations needed
- Reference related issues if applicable
Run
Step 1: Detect Project Stack
Detect the project type to determine the correct validation and scope conventions:
# Detect project type from config files
if [ -f "Package.swift" ]; then
echo "STACK=swift"
elif [ -f "pyproject.toml" ] || [ -f "setup.py" ]; then
echo "STACK=python"
elif [ -f "next.config.js" ] || [ -f "next.config.ts" ] || [ -f "next.config.mjs" ]; then
echo "STACK=nextjs"
elif [ -f "package.json" ]; then
echo "STACK=node"
fi
Step 2: Analyze Staged Changes
git branch --show-current
git status
git diff --staged --stat
git diff --staged
Step 3: Create Commit
Examine staged changes and determine type, scope, and description:
- Type:
feat,fix,refactor,perf,test,docs,style,chore - Scope (optional): derive from the primary area affected
- Description: concise summary of what changed and why
git commit -m "<type>(<scope>): <description>"
Step 4: Push to Remote
git push -u origin HEAD
Step 5: Detect Base Branch
# Fetch known integration branches
git fetch origin --no-tags 2>/dev/null
BASE=staging
best_distance=""
for candidate in staging production main master develop; do
mb=$(git merge-base HEAD "origin/$candidate" 2>/dev/null) || continue
distance=$(git rev-list --count "$mb"..HEAD 2>/dev/null) || continue
if [[ -z "$best_distance" ]] || [[ "$distance" -lt "$best_distance" ]]; then
best_distance=$distance
BASE=$candidate
fi
done
echo "Detected base: $BASE"
git log $BASE..HEAD --oneline
git diff $BASE...HEAD --stat
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 · 172 lines · 9 tokens per session scan A dede86cc725b
ship is a command published in the GitHub repository bravew/trove (10 stars, last pushed 3d ago), licensed MIT. It adds 9 tokens to every session and 1,108 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-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.