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.
git clone --depth 1 https://github.com/jubayertalha/vibeframeWrote 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/jubayertalha/vibeframe/review-drift)<a href="https://agentmods.dev/commands/jubayertalha/vibeframe/review-drift"><img src="https://agentmods.dev/badge/commands/jubayertalha/vibeframe/review-drift/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/jubayertalha/vibeframe/review-drift"><img src="https://agentmods.dev/badge/commands/jubayertalha/vibeframe/review-drift.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.00286 |
| Opus 5.5 | $0.00007 | $0.00114 |
| Sonnet 5.5 | $0.00004 | $0.00057 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
review-drift 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 1mo 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
Review and resolve open VibeFrame drift findings.
vibe_query kind=drift— open findings with evidence, most recent first.- For each finding, examine the evidence (files and lines are exact — the validator is
deterministic and does not guess):
- divergence / constraint-violation: decide whether the code or the declared design
is right. Fix the code, or declare the dependency/constraint change (and
vibe_decidewhy) so the model matches reality. - absence: implement the missing step, or remove/adjust the declared step if it was over-planned.
- broken-binding: re-link with
vibe_linkusing the candidates in the evidence. - orphan: assign the file to a component (
vibe_link component=<id> file=<glob>) or leave it and recommend dismissal if it is genuinely outside the architecture.
- divergence / constraint-violation: decide whether the code or the declared design
is right. Fix the code, or declare the dependency/constraint change (and
- After changes,
vibe_validateto confirm findings close (they auto-resolve when no longer detected). - Report anything that needs a human verdict (accept-as-new-intent or dismiss) with your recommendation — those verbs belong to the human in the browser UI.
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.
- 1mo ago First seen · 22 lines · 18 tokens per session scan A 4fb07081ca90
review-drift is a command published in the GitHub repository jubayertalha/vibeframe (0 stars, last pushed 1mo ago), licensed MIT. It adds 18 tokens to every session and 286 once invoked, about $0.0001 per session on Opus 5.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
fix
A code-repair command that detects and fixes errors reported by language servers, linters, or type checkers. These tools find code problems such as invalid syntax, style issues, and mismatched data types.
clean
A command for finding code that is no longer used and removing it after checking that tests still pass.
adr-check
Check the current change, or a plan, against the decisions that govern it and report a verdict per decision. Read-only.
sruja-bugfix-triage
Systematic workflow for triaging and fixing bugs with architecture grounding.
debug
Systematic root-cause investigation, then fix with TDD — never proposes a fix before finding the cause; resumable diagnosis + regression test in .orc/ state. Workspace-aware. For a quick one-off look without session state, prefer the bundled /debug.
optimize
Suggest concrete performance improvements for the given file or directory.