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 querygit 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/query)<a href="https://agentmods.dev/skills/rjroy/vibe-garden/query"><img src="https://agentmods.dev/badge/skills/rjroy/vibe-garden/query/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/query"><img src="https://agentmods.dev/badge/skills/rjroy/vibe-garden/query.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.00053 | $0.00833 |
| Opus 5.5 | $0.00021 | $0.00333 |
| Sonnet 5.5 | $0.00011 | $0.00167 |
| Haiku 4.5 | $0.00005 | $0.00083 |
Grade A, and why
query 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 17d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Query
Answer a question using the project wiki and relevant work artifacts. Cite every source and distinguish current, implementation-backed understanding from historical context. Offer to persist the answer as a synthesis page when it would add useful knowledge.
Gathering sources
Read the field-guide index first. Prefer .lore/reference/index.md; if it does not exist, read .lore/reference/index.html. Scan all listed pages to identify which are relevant to the question. Relevance is broad — include any page whose subject could bear on the answer, even indirectly.
Read every candidate page in full. Candidate pages may be Markdown or HTML. For HTML pages, use meta tags as metadata and visible body content as the page body. Scan relevant .lore/work/ documents for context not in the wiki. Historical brainstorms, designs, intents, research, and retros can suggest context or investigation leads; plans, notes, and tasks are not reference sources. None of these artifacts establishes current behavior or overrides current user direction. Verify current behavior claims against implementation/tests; identify unverified rationale as historical context. Where current direction conflicts with old artifacts, follow current direction and mention concrete safety or compatibility consequences when relevant, not old-document noncompliance.
If no relevant material exists, say so. Don't synthesize an answer from general knowledge when the question is asking what this project specifically decided or learned. Do not create a synthesis page that merely duplicates existing implementation or reference material; no page is a valid outcome.
Answering
Give a direct answer, then the supporting evidence. Distinguish actual current implementation from historical intentions or rationale. If historical sources conflict, identify their context without treating the conflict as a current requirement or blocking ambiguity. If code/tests and a reference conflict, report the observed behavior and the reference drift.
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.
- 17d ago Changed dd4217a9536c
- 1mo ago First seen · 53 lines · 53 tokens per session scan A 6895d919aff0
query is a skill published in the GitHub repository rjroy/vibe-garden (6 stars, last pushed 18d ago), licensed MIT. It adds 53 tokens to every session and 833 once invoked, about $0.0002 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 skills, from other repositories
pace-learn
A knowledge-management process that records reusable lessons and patterns from completed reviews, failed checks, rejected work, and signs of struggle.
new
Start a new session — save summary to memory, then mark as reset so next message gets a fresh greeting. OpenClaw-compatible. Triggers on /new, /reset, /agent:new, "nueva sesión", "new session", "reset".
alive-morning
Morning briefing -- read all walnut states, surface priorities, inbox count, stale walnuts, people nudges.
fresh-start
Continue in a new chat without losing anything — writes a compact handoff to paste into a fresh conversation. Use whenever the user wants to move to a new chat or conversation, hits usage limits, says replies got slow or Claude forgets earlier details, or the conversation has grown long.
token-check
Estimate how many tokens a pasted text, an attached file or the conversation so far takes, what it means for the context window and usage limits, and how to cut it. Use when the user asks how big something is in tokens, why they keep hitting limits, or whether a file is too large to send.
handoff
A session handoff tool that records important progress in a Markdown file and prepares a prompt for the next coding session. It preserves decisions, unfinished work, environment changes, and open questions.