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/overseedai/viwo/create-prgit clone --depth 1 https://github.com/OverseedAI/viwoWhat 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.00008 | $0.00275 |
| Opus 5 | $0.00004 | $0.00138 |
| Sonnet 5 | $0.00002 | $0.00055 |
| Haiku 4.5 | $0.00001 | $0.00028 |
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 3d 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.
This is a copy
88% identical to commit-push-pr — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Context
- Current git status: !
git status - Current git diff (staged and unstaged changes): !
git diff HEAD - Current branch: !
git branch --show-current
Your task
Based on the above changes:
- Create a new branch if on main
- If there are unstaged changes, make a commit with a message that summarizes changes.
- Push the branch to origin
- Create a pull request using
gh pr create. If your current branch starts withdev-###, always start the PR title with[DEV-###]and use the remaining branch name as the PR title. - For the description, summarize the
git diffin 23 lines for short PRs and 45 lines for big PRs. - You have the capability to call multiple tools in a single response. You MUST do all of the above in a single message. Do not use any other tools or do anything else. Do not send any other text or messages besides these tool calls.
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.
- 3d ago First seen · 22 lines · 8 tokens per session scan A e5c9ed07fc97
create-pr is a command published in the GitHub repository OverseedAI/viwo (62 stars, last pushed 4mo ago), licensed MIT. It adds 8 tokens to every session and 275 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to commit-push-pr, differing in 8 lines, and is treated as a copy.
Other commands, from other repositories
pr-submit
Create git commit and submit current branch with Graphite (squashes commits and rebases stack).
ship
Commit all changes, push branch, create/update PR, and run local validation.
speckit.aftercode
Automatically execute the subsequent code delivery pipeline: skilltypesync → changelog → commit → prgenerate, in strict sequential order.
commit-push-pr
Commit, push, and open a PR.
ship
Create a new git branch, commit changes, and create a pull request.
ship
Ship: review gate, tests, version bump, changelog, conventional commit, docs update, PR. Complete pipeline from done to merged.