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/sijeeshmiziha/visionagent/prgit clone --depth 1 https://github.com/sijeeshmiziha/visionagentWrote 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/commands/sijeeshmiziha/visionagent/pr)<a href="https://agentmods.dev/commands/sijeeshmiziha/visionagent/pr"><img src="https://agentmods.dev/badge/commands/sijeeshmiziha/visionagent/pr.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00270 |
| Opus 5 | $0.00000 | $0.00135 |
| Sonnet 5 | $0.00000 | $0.00054 |
| Haiku 4.5 | $0.00000 | $0.00027 |
Grade A, and why
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 4d 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
Create Pull Request
Create a well-structured PR for the current branch's changes.
Arguments
$ARGUMENTS (Optional: PR title or description hints)
Steps
1. Verify CI is Green
npm run ci
Do NOT create a PR if CI fails. Fix issues first.
2. Gather Context
git log main...HEAD --oneline
git diff main...HEAD --stat
Read all changed files to understand the full scope of changes.
3. Craft PR Content
Title format:
feat: <description>— new featurefix: <description>— bug fixrefactor: <description>— code cleanupdocs: <description>— documentation onlytest: <description>— tests onlychore: <description>— tooling, deps, config
Body must include:
- What changed and why
- How to test it
- Any breaking changes
- Screenshots/examples if it's a UI or output change
4. Create PR
gh pr create --title "..." --body "..."
Use HEREDOC for body formatting.
5. Report
Return the PR URL.
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.
- 4d ago First seen · 58 lines · 0 tokens per session scan A 1331aa3e0077
pr is a command published in the GitHub repository sijeeshmiziha/visionagent (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 270 tokens. 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
test-tools
Test MCP NixOS Tools (project).
release
Review and publish the Release Please release PR, then verify every registry.
checkpoint
Write a new link in the continuum chain summarizing decisions/changes since the last link.
dream
Roll up the last N links into a single phase-digest link; originals move to archived/ (never deleted).
adversarial-review
Run a Grok adversarial review that challenges the design and surfaces failure modes.
imagine
Generate an image from a text description using Grok's /imagine builtin.