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/gkaria/vibe-learnWrote 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/gkaria/vibe-learn/marketplace)<a href="https://agentmods.dev/plugins/gkaria/vibe-learn/marketplace"><img src="https://agentmods.dev/badge/plugins/gkaria/vibe-learn/marketplace/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/gkaria/vibe-learn/marketplace"><img src="https://agentmods.dev/badge/plugins/gkaria/vibe-learn/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
vibe-learn marketplace 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 2d 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": "vibe-learn",
"description": "Learn as your AI coding assistant builds.",
"owner": {
"name": "Gaurang Karia",
"url": "https://github.com/gkaria"
},
"plugins": [
{
"name": "vibe-learn",
"description": "Logs every file write, edit, and command your assistant makes, then explains, digests, and quizzes you on what was built. Offline, bash + jq, no API keys.",
"source": {
"source": "github",
"repo": "gkaria/vibe-learn"
},
"category": "learning",
"tags": ["learning", "quiz", "spaced-repetition", "session-log", "hooks"],
"homepage": "https://github.com/gkaria/vibe-learn",
"license": "MIT"
}
]
}
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
What ships with it
1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 23 lines scan A 4a1db8f00361
vibe-learn marketplace is a plugin published in the GitHub repository gkaria/vibe-learn (54 stars, last pushed yesterday), 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-09-07.
Other plugins, from other repositories
procoder
A harness that gives AI coders the tools and skills to work like a senior developer. All nine domains shipped: security, best practices, maintainability, performance, documentation, clean code, CI/CD, DevOps, GitOps — plus the code index. Hooks hand the agent results; the agent stays in control.
procoder
A harness that gives AI coders the tools and skills to work like a senior developer.
academic
Academic — 2 free + 1 paid (Credits redemption required).
x-dev-pipeline
Structured dev workflow with spec, user-global risk RAG, task breakdown, execution, verify, qa-gate, fix loops, and audits.
explain
Structured code explainer — layered explanations of files, functions, directories, or concepts.
make-skill
Create, retrofit, audit, and ship agent skills & Claude Code plugins the proven ssheleg way: conformance to the Agent Skills open standard, Anthropic's platform rules (surfaces, Skills API, evals) and the Claude Code plugin reference, marketplace repo layout, version sync, validator + CI, multi-channel distribution…