laravel-plugin-discovery

laravel-plugin-discovery is a skill for Claude Code, Codex from JunMystery/Agent-Guidance-Python. It costs 37 tokens per session (1,508 once invoked), scanned A, a copy of laravel-plugin-discovery, MIT.

A tool for finding and evaluating Laravel packages, which are reusable PHP components for Laravel applications.

In plain words
What is it for?
Searching for Laravel packages by feature, checking package health, and confirming Laravel or PHP compatibility.
Why use it?
It helps developers compare packages, check maintenance health, and verify compatibility before adding dependencies.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/junmystery/agent-guidance-python/laravel-plugin-discovery
Any agent
npx skills add JunMystery/Agent-Guidance-Python --skill laravel-plugin-discovery
Clone the repo
git clone --depth 1 https://github.com/JunMystery/Agent-Guidance-Python

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for laravel-plugin-discovery

README.md
[![agentmods](https://agentmods.dev/badge/skills/junmystery/agent-guidance-python/laravel-plugin-discovery.svg)](https://agentmods.dev/skills/junmystery/agent-guidance-python/laravel-plugin-discovery)
Your own site
<a href="https://agentmods.dev/skills/junmystery/agent-guidance-python/laravel-plugin-discovery"><img src="https://agentmods.dev/badge/skills/junmystery/agent-guidance-python/laravel-plugin-discovery.svg" alt="Measured on agentmods" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,508 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 95% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured yesterday against content hash 29363db6147b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

Origin

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.

skills/laravel-plugin-discovery/SKILL.md · 230 lines

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 ~/.claude.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, or Unrated
  • laravel_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:

  1. Use SearchPluginTool with relevant keywords
  2. Apply filters for health score, Laravel version, or PHP version
  3. Review the results with package names, descriptions, and health indicators

Read the full file on GitHub · 230 lines

Changes

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.

  1. yesterday First seen · 230 lines · 37 tokens per session scan A 29363db6147b

Subscribe to this mod's changes

laravel-plugin-discovery is a skill published in the GitHub repository JunMystery/Agent-Guidance-Python (2 stars, last pushed 1mo 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.

Related

Other skills, from other repositories

laravel-security

Use when building, configuring, or hardening security-sensitive Laravel features — authentication, authorization, Eloquent safety, CSRF/XSS, API security, file uploads, secrets, and production configuration. Provides condensed, copy-ready secure defaults for Laravel 11 / PHP 8.3.

pekral/cursor-rules · 61 tokens

scraperapi-php-sdk

Best-practices reference for the ScraperAPI PHP SDK (scraperapi/sdk Composer package). Consult whenever the user is writing, debugging, or reviewing PHP code that calls ScraperAPI. Use when user asks: "scrape a website with PHP and ScraperAPI", "ScraperAPI PHP example", "how do I use the ScraperAPI PHP SDK", "PHP…

scraperapi/scraperapi-skills · 154 tokens

class-refactoring

Use when refactor PHP classes to improve structure, readability, and maintainability while preserving behavior.

pekral/cursor-rules · 22 tokens

benchmark-optimization-loop

Use when a goal is vague speed ("make it faster", "reduce p95", "cut query time") and you need a bounded, measured loop that promotes only verified, correctness-preserving wins instead of guessed micro-tweaks.

pekral/cursor-rules · 52 tokens

rewrite-tests-pest

Use when rewriting existing tests to Pest syntax. Preserve behavior, follow project testing conventions, reduce duplication where helpful, and verify rewritten tests are deterministic and passing.

pekral/cursor-rules · 36 tokens

composer-update

Use when analyze composer update results, detect conflicts, and summarize changelogs of updated dependencies.

pekral/cursor-rules · 21 tokens