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/pekral/cursor-rulesWrote 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/rules/pekral/cursor-rules/dependency-selection)<a href="https://agentmods.dev/rules/pekral/cursor-rules/dependency-selection"><img src="https://agentmods.dev/badge/rules/pekral/cursor-rules/dependency-selection/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/rules/pekral/cursor-rules/dependency-selection"><img src="https://agentmods.dev/badge/rules/pekral/cursor-rules/dependency-selection.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00022 | $0.01987 |
| Opus 5.5 | $0.00009 | $0.00795 |
| Sonnet 5.5 | $0.00004 | $0.00397 |
| Haiku 4.5 | $0.00002 | $0.00199 |
Grade A, and why
dependency-selection 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scope
Apply this rule every time a skill needs to propose a new Composer dependency — whether the package is being looked up on Packagist (the default registry), on GitHub directly (VCS repository, private fork, unpublished package), or on any other Composer-compatible source. The goal is to keep the project off abandoned and unmaintained libraries and to make the selection auditable.
The rule does not trigger for:
- bumping a version of a package that is already in
composer.json— that is owned by@skills/composer-update/SKILL.md(the activity gate below still applies if the bump uncovers an abandoned upstream) - removing a package — no activity check needed
- internal
pekral/*or other first-party packages owned by the same organisation — the Activity gate below is informational only, the Compatibility gate still applies
Activity gate (mandatory — every candidate must pass before it can be considered)
A candidate package qualifies only when all of the following hold. Evaluate each candidate against the canonical source (Packagist for registered packages, the GitHub repository for VCS / unregistered packages) — never guess from memory or from the package name alone.
- Recent activity (≤ 12 months). The most recent commit on the default branch and the most recent tagged release must both be no older than 12 months from today's date. A package with a recent commit but no release in the last 12 months still qualifies only when the recent commit is on the default branch and the project's release cadence (visible from prior tags) is documented as low-frequency-by-design (PSR specs, mature standalone utilities). Cite the documented cadence in the selection note.
- Not archived. The GitHub repository must not be archived (
archived: falsein the repo metadata). - Not abandoned on Packagist. When the candidate is registered on Packagist, the package page must not carry the
abandonedflag. When abandoned with a documented replacement, follow the replacement pointer and re-run the whole selection against the suggested successor — never adopt an abandoned package even if it still appears active on GitHub. - Tagged release exists. The repository ships at least one Composer-installable tagged release (
v*,*.*.*, or any SemVer tag Composer recognises). Composer'sdev-main/dev-masterconstraints do not qualify a candidate; depending on a moving branch is prohibited. - Issue tracker is responsive. Open issues / PRs receive at least one maintainer reply within the last 12 months. A repository with > 50 open issues and zero maintainer activity in the last 12 months fails this gate even when the commit history looks healthy (drive-by commits without triage are not maintenance).
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.
- 1mo ago First seen · 78 lines · 22 tokens per session scan A b471734fa3e8
dependency-selection is a cursor rule published in the GitHub repository pekral/cursor-rules (11 stars, last pushed 13d ago), licensed MIT. It adds 22 tokens to every session and 1,987 once invoked, about $0.0001 per session on Opus 5.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 cursor rules, from other repositories
php
Rules applied when working in PHP files (incl. Laravel, Symfony, WordPress).
laravel-boost
Cursor rule "laravel-boost" from karuhun-developer/ecommerce, covering laravel boost guidelines, foundational context, conventions, verification scripts and application structure & architecture.
laravel-boost
Cursor rule "laravel-boost" from laravel/locket, covering laravel boost guidelines, foundational context, conventions, verification scripts and application structure & architecture.
php-drupal-best-practices
PHP & Drupal Development Standards and Best Practices.
10-backend
Backend development rules for Laravel Admin applications, including route locations, controller structure, permissions, API responses, and list filtering. Laravel is a PHP framework for building web applications.
laravel
Laravel: Eloquent, Form Requests, policies.