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/usrrname/cursorrules/laravelnpx skills add usrrname/cursorrules --skill laravelgit clone --depth 1 https://github.com/usrrname/cursorrulesWhat 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.00008 | $0.00372 |
| Opus 5 | $0.00004 | $0.00186 |
| Sonnet 5 | $0.00002 | $0.00074 |
| Haiku 4.5 | $0.00001 | $0.00037 |
Grade A, and why
laravel 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
Laravel Skill
Build robust PHP applications with Laravel framework.
When to Use
- Creating Laravel applications
- Building APIs with Laravel
- Writing Eloquent models
- Implementing authentication
Critical Rules
Architecture
- Follow MVC pattern
- Use Service classes for business logic
- Implement Repository pattern for data access
- Use Form Request classes for validation
- Keep controllers thin, models rich
Eloquent ORM
- Use eager loading to avoid N+1 queries
- Define relationships explicitly
- Use accessors/mutators sparingly
- Leverage query scopes
- Use factories for testing
Security
- Use Laravel's authentication system
- Hash passwords with bcrypt
- Use CSRF protection on forms
- Sanitize user inputs
- Use authorization gates/policies
Code Style
- Follow PSR-12 coding standards
- Use type hints
- Leverage Laravel's helper functions
- Write docblocks for complex methods
- Use meaningful variable names
Examples
Good
class UserController extends Controller
{
public function index(Request $request): JsonResponse
{
$users = User::with('posts')
->active()
->paginate(20);
return response()->json($users);
}
}
Bad
// N+1 query problem
$users = User::all();
foreach ($users as $user) {
echo $user->posts->count(); // Query in loop
}
Related
/mysql- Database patterns/typescript- For API type definitions
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 · 81 lines · 8 tokens per session scan A c79c8874172a
laravel is a skill published in the GitHub repository usrrname/cursorrules (10 stars, last pushed 4mo ago), licensed ISC. It adds 8 tokens to every session and 372 once invoked, about $0.0000 per session on Opus 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
Release Notes Generation
Mandatory fast-mcp-telegram release workflow. Use when the user says release, merge and release, bump version, tag, gh release, PyPI publish, or Telegram version announcement.
sourcery-pr-cycle
Runs the PR creation and Sourcery AI review loop until merge-ready: open PR with gh, poll checks and comments, fix blocking issues, push, re-request review, repeat. Use when the user asks to create a PR, run the Sourcery cycle, address Sourcery review comments, or get a branch merge-ready after review.
feature-development
Feature development workflow for Telegram MCP projects. Use when implementing new features including research, planning, implementation, testing, and documentation.
telegram-patterns
Telegram-specific patterns and Telethon library usage.
Clean Up Docs Push
Code cleanup, docs update, and git push workflow.
Remove Old Logs
Remove log files older than 1 day from logs directory.