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/edimuj/vexscan/releasegit clone --depth 1 https://github.com/edimuj/vexscanWrote 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/edimuj/vexscan/release)<a href="https://agentmods.dev/commands/edimuj/vexscan/release"><img src="https://agentmods.dev/badge/commands/edimuj/vexscan/release.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.00017 | $0.00958 |
| Opus 5 | $0.00009 | $0.00479 |
| Sonnet 5 | $0.00003 | $0.00192 |
| Haiku 4.5 | $0.00002 | $0.00096 |
Grade A, and why
release 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.
How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release vexscan
You are releasing a new version of vexscan.
Step 1: Pre-flight checks
Run these sequentially. If any fail, stop immediately and report the failure.
cargo fmt -- --check
cargo clippy -- -D warnings
cargo nextest run
cargo run -- rules test
Then verify the working tree is clean:
git status --porcelain
If there are uncommitted changes, stop and tell the user to commit or stash first.
Step 2: Determine version bump
Read the current version from Cargo.toml (the version = "X.Y.Z" line).
If $ARGUMENTS is patch, minor, or major: use that directly. Skip analysis.
If $ARGUMENTS is empty: analyze the changes since the last git tag to determine the bump type.
git describe --tags --abbrev=0
git log <last-tag>..HEAD --oneline
git diff <last-tag>..HEAD --stat
Read the actual commit diffs if the summary isn't clear enough. Then classify:
- patch — bug fixes, formatting fixes, rule pattern tweaks, doc typos, dependency updates, CI fixes
- minor — new features, new commands, new detection rules, new output formats, new CLI flags, significant refactors that change behavior
- major — breaking CLI changes (removed/renamed flags, changed output format defaults), breaking config file format changes, removed commands
If you determine major: ask the user for confirmation before proceeding. Explain what breaking changes you found.
If patch or minor: tell the user your reasoning in one line and proceed. Example: "Minor bump — new check command and trust store feature since v0.11.0"
Apply the bump:
patch→ increment patchminor→ increment minor, reset patch to 0major→ increment major, reset minor and patch to 0
Tell the user: "Releasing vX.Y.Z (was A.B.C)"
Step 3: Bump version
Edit Cargo.toml — update the version = "..." line to the new version.
Then rebuild to update Cargo.lock:
cargo build --release
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 · 124 lines · 17 tokens per session scan A 4ddc147d398f
release is a command published in the GitHub repository edimuj/vexscan (9 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 958 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
release
Run ../../hooks/session-start.ps1 and ../../scripts/release.py.
review-renovate
Review and merge renovate PRs with automerge configuration updates.
release
Perform a full release: generate release notes, bump version, commit, tag, and push.
release
Create a full stable release for the project. Optionally pass a title suffix (e.g., "Template Presets Fix") or extra notes.
SHIP_RELEASE
Ship the active release/X.Y.Z — build the installer, merge to main, tag, push, and publish the GitHub release. Run after /prerelease passes.
release
The pre-tag controller: version sync, changelog, clean tree, gate, and suite — every failure listed, the tag printed, never run.