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/reconcile)<a href="https://agentmods.dev/commands/jubayertalha/vibeframe/reconcile"><img src="https://agentmods.dev/badge/commands/jubayertalha/vibeframe/reconcile.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.1 | $0.00014 | $0.00218 |
| Opus 5 | $0.00007 | $0.00109 |
| Sonnet 5 | $0.00003 | $0.00044 |
| Haiku 4.5 | $0.00001 | $0.00022 |
Grade A, and why
reconcile 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 7d 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
Reconcile the VibeFrame model with unexplained code changes.
vibe_query kind=reconcile— the queue of changed paths no task or declaration explains.- For each path:
vibe_query kind=inspect ref=<path>to see its symbols, owner component, and any steps already bound to it. Read the file if needed. - Decide what the change means and record exactly that:
- implements a declared step →
vibe_linkthe step to the symbol; - new behavior →
vibe_declarethe missing workflow/step (and component changes); - design shift worth remembering →
vibe_decide; - incidental (formatting, comments, refactor with no model impact) → note it and move on.
- implements a declared step →
- Finish with
vibe_validateand report: what was explained, what was declared, anything you recommend the human accept or dismiss.
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.
- 7d ago First seen · 19 lines · 14 tokens per session scan A 45f1919428c8
reconcile is a command published in the GitHub repository jubayertalha/vibeframe (0 stars, last pushed 10d ago), licensed MIT. It adds 14 tokens to every session and 218 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
taskstoissues
A command that turns structured tasks from project design documents into ordered GitHub Issues, written in simplified Chinese.
resume-project
Run resume-project now — Now / Blocked / Next. Not a cheat sheet.
status
The state of play, computed fresh: branch, dirty files, the active sprint, open work, index freshness.
sddp-implement
Command description: Implement the current feature tasks. Argument hint: [optional: phase or task to start from] Command category: feature-delivery Prerequisites: spec, plan, tasks, checklists:complete-if-present.
aft
Transfer feature from its current agent to a different agent — preserves commits and in-flight work (shortcut for feature-transfer).
afs
Start feature [agents...] - create workspace and begin implementation (shortcut for feature-start).