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/jubayertalha/vibeframe/plan-featuregit 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/plan-feature)<a href="https://agentmods.dev/commands/jubayertalha/vibeframe/plan-feature"><img src="https://agentmods.dev/badge/commands/jubayertalha/vibeframe/plan-feature.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.00022 | $0.00247 |
| Opus 5 | $0.00011 | $0.00123 |
| Sonnet 5 | $0.00004 | $0.00049 |
| Haiku 4.5 | $0.00002 | $0.00025 |
Grade A, and why
plan-feature 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
Plan and implement: $ARGUMENTS
- Call
vibe_contextwith this topic and read the brief. Respect LOCKED decisions and machine-checked constraints — they are requirements, not suggestions. vibe_task action=startwith a clear title and the refs involved.- Declare the intent BEFORE writing code:
vibe_declarethe capability/workflow with 5–15 concrete steps (each assigned to a component; add components and theirdependsOnallowances as needed), andvibe_decideanything a future reader will ask "why" about. - Implement the steps.
- Bind each implemented step with
vibe_link(preferpath#Symbolmonikers). vibe_validate— resolve every error finding: fix the code, or update the model when reality should win.vibe_task action=finishand handle anything it reports (reconcile queue, open findings).
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 · 21 lines · 22 tokens per session scan A 9d757895016e
plan-feature is a command published in the GitHub repository jubayertalha/vibeframe (0 stars, last pushed 7d ago), licensed MIT. It adds 22 tokens to every session and 247 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
adr-backfill
Audit code, documentation, and history for potential architecture decisions that were never recorded, then return a deduplicated evidence report. Read-only.
adr-draft
Draft one new ADR from a current decision or a selected backfill handoff. Writes a single new record, as proposed.
adr-check
Check the current change, or a plan, against the decisions that govern it and report a verdict per decision. Read-only.
adr-queue
Show the review queue — every decision still proposed, with its SLA state — so open questions are visible before they are planned around. Read-only.
adr-context
Load the architecture decisions that govern the paths you are about to change, before planning against them. Read-only.
check
Check a produced plan against the decisions that govern it. Read-only.