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/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/plugins/rjroy/vibe-garden/lore-development)<a href="https://agentmods.dev/plugins/rjroy/vibe-garden/lore-development"><img src="https://agentmods.dev/badge/plugins/rjroy/vibe-garden/lore-development/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/plugins/rjroy/vibe-garden/lore-development"><img src="https://agentmods.dev/badge/plugins/rjroy/vibe-garden/lore-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
lore-development 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.
What it actually says
{
"name": "lore-development",
"description": "A lightweight plugin for building project context. Skills for research, brainstorming, intent, design, planning, implementation, and retrospectives.",
"version": "4.0.0",
"author": {
"name": "Ronald Roy",
"email": "[email protected]"
}
}
What it installs
The manifest is a name and a version. 14 skills, 6 agents travel with it, and installing the plugin installs all of them — 973 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill install-formula A 31 tokens
- Skill implement A 58 tokens
- Skill migrate A 52 tokens
- Skill prep-plan A 74 tokens
- Skill intent A 53 tokens
- Skill simplify A 31 tokens
- Skill vision A 78 tokens
- Skill define-validation A 41 tokens
- Skill design A 70 tokens
- Skill refactor A 38 tokens
- Skill retro A 65 tokens
- Skill brainstorm A 52 tokens
- Skill research A 57 tokens
- Skill poke-holes A 69 tokens
- Agent bun-typescript-reviewer A 34 tokens
- Agent plan-reviewer A 24 tokens
- Agent design-reviewer A 26 tokens
- Agent lore-researcher A 63 tokens
- Agent intent-reviewer A 29 tokens
- Agent rust-daemon-cli-reviewer A 28 tokens
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 Changed 3b7cd7249b08
- 1mo ago First seen · 10 lines scan A 38991d302d9a
lore-development is a plugin published in the GitHub repository rjroy/vibe-garden (6 stars, last pushed 10d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
team-motivation
Team motivation and management skills including Daniel Pink's Autonomy, Mastery, Purpose (AMP) principles and Andy Grove's High Output Management (leverage, one-on-ones, OKRs, task-relevant maturity).
catchup
Async-team return-from-absence briefing. /catchup fans out to GitHub, git, Linear, and calendar, then emits one prioritized Context Brief instead of a firehose.
piyaz
Persistent context network for coding projects. Tracks tasks, dependencies, and decisions across sessions.
workhub
Task-board, schedule and vault knowledge-base skills and hooks for the workhub vault (task-list, task-start, task-report, task-handoff, task-chain, task-orchestrate, project-start, shared-space, diagram-edit, vault-init, vault-setup, vault-migrate, vault-upgrade, kb-ingest, kb-query, kb-lint, kb-index, strategist)…
telegram-topics
Telegram channel for Claude Code — 1 project = 1 forum topic, with a live working/idle status badge on each topic. Run multiple projects concurrently, get notifications, and drive or approve sessions remotely from your phone. Configure with /telegram-topics:configure.
standup
Records what every Claude Code session actually shipped, then renders it as a page you can read before standup.