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/pekral/cursor-rules/composer-updatenpx skills add pekral/cursor-rules --skill composer-updategit clone --depth 1 https://github.com/pekral/cursor-rulesWhat 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.00021 | $0.00470 |
| Opus 5 | $0.00010 | $0.00235 |
| Sonnet 5 | $0.00004 | $0.00094 |
| Haiku 4.5 | $0.00002 | $0.00047 |
Grade A, and why
composer-update 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 3d 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
Composer Update
Purpose
Analyze dependency updates after composer update, detect conflicts, and summarize relevant changes.
Constraints
- Apply @rules/php/core-standards.mdc
- Apply @rules/php/dependency-selection.mdc — this skill primarily bumps existing packages (rule out of scope per its Scope section), but a bump frequently uncovers an upstream that has been archived or marked abandoned. When that happens, re-run the Activity gate + Compatibility gate against the suggested replacement (or against a fresh search if no replacement is documented) before recommending the migration. Never silently keep an archived / abandoned package in the lockfile just because the bump compiles.
- Output Markdown only
Execution
1. Update Context
- Use output from
composer updateif available - Otherwise compare current
composer.lockwith the previous version
2. Detect Updated Packages
- List all added or changed packages
- Include version changes:
old → new
3. Conflict Detection
- Identify dependency conflicts from:
- composer output
- version constraint mismatches (
composer.jsonvscomposer.lock)
- Summarize conflicts clearly (package → reason)
- If none: state "No conflicts detected"
4. Changelog Extraction
For each updated package:
-
Prefer:
vendor/<package>/CHANGELOG*
-
Fallback:
- repository releases (GitHub/GitLab)
- package homepage
-
Extract:
- breaking changes
- new features
- important fixes
-
If unavailable:
- state "No changelog found"
5. Suggested Follow-up
- Recommend relevant checks:
- run tests
composer validatecomposer audit
Output Format
Use the template defined in templates/update-report.md.
Principles
- Focus on impactful changes, not noise
- Highlight breaking changes first
- Prefer local sources over remote
- Be concise and actionable
- Highlight security-related changes when present
What ships with it
1 file beside SKILL.md 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.
- 3d ago First seen · 78 lines · 21 tokens per session scan A 0a8c3eb52225
composer-update is a skill published in the GitHub repository pekral/cursor-rules (6 stars, last pushed 8d ago), licensed MIT. It adds 21 tokens to every session and 470 once invoked, about $0.0001 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
migrate-radix-to-base
Migrates React projects and components from Radix UI to Base UI. Use when asked to migrate from radix, move to base-ui, convert radix primitives, or switch a shadcn project's base library. Handles single components ("migrate accordion") and whole projects.
ponytail-gain
Show ponytail measured impact as a scoreboard: less code, less cost, more speed, from the benchmark medians. One-shot display.
parse-table
Parse table definition to extract module name, model name, table name, and field definitions. First step of CRUD generation.
owl-admin-ops-commands
Use this skill for Owl Admin installation, publishing assets, upgrades, diagnostics, database inspection, menu maintenance, user creation, password reset, route generation, IDE helper, admin:publish, admin:install, admin:update, admin:doctor, admin:db, admin:menu, admin:create-user, or deployment troubleshooting.
octane-development
Use this skill when working with Laravel Octane, a long-running PHP worker server (Swoole, FrankenPHP, RoadRunner) where the application boots once and serves many requests instead of rebooting for each request like PHP-FPM. Trigger when installing Octane or starting its server; configuring or detecting the active…
module:assistant
Add an AI assistant chat panel to any Laravel project — with tool calling, streaming, and MCP support.