Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add jx-hxxx/hi-vibe/plugin install hi-vibeWrote 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/jx-hxxx/hi-vibe/log)<a href="https://agentmods.dev/commands/jx-hxxx/hi-vibe/log"><img src="https://agentmods.dev/badge/commands/jx-hxxx/hi-vibe/log/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/jx-hxxx/hi-vibe/log"><img src="https://agentmods.dev/badge/commands/jx-hxxx/hi-vibe/log.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00018 | $0.00067 |
| Opus 5 | $0.00009 | $0.00034 |
| Sonnet 5 | $0.00004 | $0.00013 |
| Haiku 4.5 | $0.00002 | $0.00007 |
Grade A, and why
log 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 10d 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
Read ${CLAUDE_PLUGIN_ROOT}/skills/docs-keeper/SKILL.md.
Mode: log
Arguments: $ARGUMENTS
Follow that mode exactly.
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.
- 10d ago First seen · 12 lines · 18 tokens per session scan A d1c18e5d2be0
log is a command published in the GitHub repository jx-hxxx/hi-vibe (3 stars, last pushed 5d ago), licensed MIT. It adds 18 tokens to every session and 67 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
Guided release for the skill-engine repo. Bumps the six version surfaces, drafts the CHANGELOG entry, runs validators, then pauses for the maintainer to commit, push, and tag manually. Accepts major / minor / patch / explicit X.Y.Z.
doc-refresh
Refresh documentation after version bumps, feature additions, or periodic maintenance: $ARGUMENTS.
changelog
Generate or update CHANGELOG.md from git history: $ARGUMENTS.
merge
Finish a PR properly: every check green, every review addressed — human and bot — then merge and clean up.
pr
Prepare and open a pull request the senior way: gate, template, scrubbed, everything visible.
release
The pre-tag controller: version sync, changelog, clean tree, gate, and suite — every failure listed, the tag printed, never run.