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 initgit 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/init)<a href="https://agentmods.dev/skills/rjroy/vibe-garden/init"><img src="https://agentmods.dev/badge/skills/rjroy/vibe-garden/init/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/init"><img src="https://agentmods.dev/badge/skills/rjroy/vibe-garden/init.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.00054 | $0.01213 |
| Opus 5.5 | $0.00022 | $0.00485 |
| Sonnet 5.5 | $0.00011 | $0.00243 |
| Haiku 4.5 | $0.00005 | $0.00121 |
Grade A, and why
init 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Init
Bootstrap the project wiki, ensure disposable local lore output is ignored when the lore-development setup helper is available, and register a scheduled lint job.
Dependencies
CronCreate and CronList are only required for scheduling. Project/wiki setup
does not depend on Cron availability. The local-lore ignore setup is provided
by lore-development's scripts/ensure_local.py; when plugins are installed as
siblings, resolve ../../../lore-development/scripts/ensure_local.py relative
to this skill's installed location, then run it with python3 <resolved-helper-path> <explicit-project-root>.
Do not guess the project root or a global helper path. If lore-development is
installed separately and the sibling helper is unavailable, report that the
optional helper is unavailable; users can run python3 <path-to-lore-development>/scripts/ensure_local.py <project-root> directly. This standalone
helper requires Python's standard library only.
If either CronCreate or CronList is unavailable in the Claude Code harness, skip all scheduling operations. Continue wiki setup and tell the user that scheduling was unavailable; do not substitute another harness's tools.
Steps
1. Create the wiki directory.
If the lore-development helper is available as described above, run it for the
project before creating any local lore output. This creates .lore/local/ and
adds the root-anchored /.lore/local/ rule to .gitignore without replacing
existing contents. Do not require the helper or Cron for wiki/index setup.
If the helper is unavailable or exits with an error, say local-lore setup did
not succeed and do not claim .lore/local/ is ready. Continue the independent
reference wiki/index setup; users can retry the helper directly.
Check whether .lore/reference/ exists. If not, create it. Then check whether .lore/reference/index.md or .lore/reference/index.html exists.
If neither index exists, write a minimal Markdown file at .lore/reference/index.md:
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 · +27 lines dd03309fdd61
- 1mo ago First seen · 73 lines · 54 tokens per session scan A 71bf106ba090
init is a skill published in the GitHub repository rjroy/vibe-garden (6 stars, last pushed 18d ago), licensed MIT. It adds 54 tokens to every session and 1,213 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.
pace-pulse
Auto-invoked during advance mode after extended work on same CR, at session start/end, or when rhythm anomalies are detected. NOT for metrics reports or retrospectives (use /pace-retro). NOT for project status overview (use /pace-status).
add-teams
Adds Microsoft Teams connector to a Power Apps code app. Use when sending Teams messages, posting to channels, or integrating with Teams chat.
sys-configure
Configure Claude Octopus — redirects to /octo:setup interactive wizard.
relations
OPS on-demand: This skill should be used when the user asks to "who do I owe a reply", "relationship…
llm-friendly-context
Clarifies inputs, outputs, success criteria, decisions, and unresolved conditions so downstream consumers can execute without guessing. Use when writing or revising LLM-facing prompts, handoffs, planning artifacts, reviews, reports, or generated instructions.