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 skills add rjroy/vibe-garden --skill install-formulagit clone --depth 1 https://github.com/rjroy/vibe-gardenWrote 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/skills/rjroy/vibe-garden/install-formula)<a href="https://agentmods.dev/skills/rjroy/vibe-garden/install-formula"><img src="https://agentmods.dev/badge/skills/rjroy/vibe-garden/install-formula/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/skills/rjroy/vibe-garden/install-formula"><img src="https://agentmods.dev/badge/skills/rjroy/vibe-garden/install-formula.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.00031 | $0.00513 |
| Opus 5.5 | $0.00012 | $0.00205 |
| Sonnet 5.5 | $0.00006 | $0.00103 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
install-formula 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 9d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Install Formula
Install the plugin's lore-development Beads formula into the current project.
Process
- From this skill's base directory, resolve the plugin root two levels up. The
source formula is at
../../formulas/lore-development.formula.toml. - Confirm the current directory is the intended project root. Do not install into a parent directory or a different checkout without the user's explicit path.
- Create
.beads/formulas/if it does not exist. - If
.beads/formulas/lore-development.formula.tomldoes not exist, copy the source formula there. - If it already exists, compare it with the plugin formula. Report that it is already installed when identical. If it differs, stop and ask whether the user wants to replace it. Never overwrite a project-owned formula silently.
- Run
bd formula show .beads/formulas/lore-development.formula.toml --jsonand verify that the parsed result contains the required variables and workflow steps, with human gates onapprove-designandapprove-plan. Intent is conversational context, not an approval gate. - Explain how to use the installed formula.
bd mol pourcan cook a formula from the project formula search path directly:
bd mol pour lore-development --var topic="..." --var artifact_name="..."
Approval Semantics
Do not replace human gates with an approved variable. Variables provide work
inputs; they do not establish that a person made a decision. A human gate remains
open until a person resolves it with bd gate resolve <gate-id>.
The formula gates design and implementation-plan approval, not intent. Intent is a conversational record of what and why, not a contract requiring approval. Implementation proceeds without a routine approval gate. If the implementation skill encounters a concrete safety or compatibility concern or a stuck correction loop, it must escalate to the user rather than inventing an approval value.
Safety
- Do not modify an existing formula without explicit user permission.
- Do not create or close molecule steps while installing the formula.
- Do not claim that a gate was approved based on a variable, prompt assumption, or agent judgment.
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.
- 9d ago First seen · 51 lines · 31 tokens per session scan A 99f1f4f586e7
install-formula is a skill published in the GitHub repository rjroy/vibe-garden (6 stars, last pushed 10d ago), licensed MIT. It adds 31 tokens to every session and 513 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-10-08.
Other skills, from other repositories
deep-project
Decomposes vague, high-level project requirements into well-scoped planning units for /deep-plan. Use when starting a new project that needs to be broken into manageable pieces.
piyaz
Use when the user wants to plan, decompose, track, or resume a multi-task project: scoping a new idea, importing or onboarding an existing repo or workspace, asking what to work on / what's next / what's blocked / where they left off, reporting task completion, dispatching work in parallel, or planning a draft task.…
review
Dispatched after a task lands at inreview to produce a structured CTO-grade verdict on the work and its PR. Two invocation paths: composer Phase 4 (orchestrator dispatches after the implementer's inreview write, surfaces the verdict to HOTL, stops), and direct mode from the piyaz skill on requests ("review VF-N"…
decompose
Use when a Piyaz project exists with a description but few or no tasks, and the user wants it broken into an implementable graph (project-level decomposition). Triggers: "decompose", "break this down", "create tasks", "turn this into tasks", "give me a task list", "plan out the work", "how should I build this". Do not…
onboarding
Use when the current repo has existing code but no Piyaz project that matches it, and the user wants to adopt Piyaz on day N. Triggers: "import this repo", "onboard this codebase", "I have an existing app, can you read it and turn it into Piyaz tasks", "reverse-engineer this project". Do not use when no code exists…
composer
Use when the user types /piyaz:composer, /piyaz:composer , or /piyaz:composer rework , or asks to run the next Piyaz task end-to-end, ship the backlog, compose through the ready queue, or loop through Piyaz tasks until done. Composer researches, refines, plans, implements, reviews, and fixes each task in a loop until…