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 agentmods add skills/jamkris/everything-gemini-code/laravel-plugin-discoverynpx skills add Jamkris/everything-gemini-code --skill laravel-plugin-discoverygit clone --depth 1 https://github.com/Jamkris/everything-gemini-codeWrote 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/jamkris/everything-gemini-code/laravel-plugin-discovery)<a href="https://agentmods.dev/skills/jamkris/everything-gemini-code/laravel-plugin-discovery"><img src="https://agentmods.dev/badge/skills/jamkris/everything-gemini-code/laravel-plugin-discovery.svg" alt="Measured on agentmods" 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 | $0.00037 | $0.01508 |
| Opus 5 | $0.00018 | $0.00754 |
| Sonnet 5 | $0.00007 | $0.00302 |
| Haiku 4.5 | $0.00004 | $0.00151 |
Grade A, and why
laravel-plugin-discovery 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 yesterday.
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.
This is a copy
95% identical to laravel-plugin-discovery — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Laravel Plugin Discovery
Find, evaluate, and choose healthy Laravel packages using the LaraPlugins.io MCP server.
When to Use
- User wants to find Laravel packages for a specific feature (e.g. "auth", "permissions", "admin panel")
- User asks "what package should I use for..." or "is there a Laravel package for..."
- User wants to check if a package is actively maintained
- User needs to verify Laravel version compatibility
- User wants to assess package health before adding to a project
MCP Requirement
LaraPlugins MCP server must be configured. Add to your ~/.gemini.json mcpServers:
"laraplugins": {
"type": "http",
"url": "https://laraplugins.io/mcp/plugins"
}
No API key required — the server is free for the Laravel community.
MCP Tools
The LaraPlugins MCP provides two primary tools:
SearchPluginTool
Search packages by keyword, health score, vendor, and version compatibility.
Parameters:
text_search(string, optional): Keyword to search (e.g. "permission", "admin", "api")health_score(string, optional): Filter by health band —Healthy,Medium,Unhealthy, orUnratedlaravel_compatibility(string, optional): Filter by Laravel version —"5","6","7","8","9","10","11","12","13"php_compatibility(string, optional): Filter by PHP version —"7.4","8.0","8.1","8.2","8.3","8.4","8.5"vendor_filter(string, optional): Filter by vendor name (e.g. "spatie", "laravel")page(number, optional): Page number for pagination
GetPluginDetailsTool
Fetch detailed metrics, readme content, and version history for a specific package.
Parameters:
package(string, required): Full Composer package name (e.g. "spatie/laravel-permission")include_versions(boolean, optional): Include version history in response
How It Works
Finding Packages
When the user wants to discover packages for a feature:
- Use
SearchPluginToolwith relevant keywords - Apply filters for health score, Laravel version, or PHP version
- Review the results with package names, descriptions, and health indicators
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.
- yesterday First seen · 230 lines · 37 tokens per session scan A f95bbb17340f
laravel-plugin-discovery is a skill published in the GitHub repository Jamkris/everything-gemini-code (87 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 1,508 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to laravel-plugin-discovery, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
php-idioms
Modern PHP (8.x) rewards type safety, immutability, and framework-agnostic design. Lean into typed properties, enums, and readonly classes. Idiomatic PHP = strict types, PSR-compliant, well-tested.
laravel-idioms
Laravel rewards convention, Eloquent, and expressive syntax. Idiomatic Laravel = DRY, service-oriented, well-tested.
laravel-expert
Laravel & PHP Development Instructions for GitHub Copilot.
mvc-expert
Expert guidelines to refactor legacy PHP codebases into clean, modern, and scalable MVC-structured projects / Pedoman ahli untuk merefaktor codebase PHP lama menjadi proyek terstruktur MVC yang bersih, modern, dan skalabel.
php-laravel-codestyle
Custom Instructions: PHP 8+ & Laravel Architecture Expert.
programming
MUST USE for ANY work on .py .pyi .rs .ts .tsx .mts .cts .go files. One philosophy: strict types, modern stacks (Pydantic v2 / serde+thiserror / Zod / gin+sqlc+pgx+slog), modern toolchains (uv+basedpyright+ruff / cargo+clippy+miri / Bun+Biome+tsc / gofumpt+golangci-lint v2+nilaway+go-race), parse-don't-validate…