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 skills add krzysztofsurdy/code-virtuoso --skill composer-dependenciesgit clone --depth 1 https://github.com/krzysztofsurdy/code-virtuosoWrote 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/krzysztofsurdy/code-virtuoso/composer-dependencies)<a href="https://agentmods.dev/skills/krzysztofsurdy/code-virtuoso/composer-dependencies"><img src="https://agentmods.dev/badge/skills/krzysztofsurdy/code-virtuoso/composer-dependencies/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/skills/krzysztofsurdy/code-virtuoso/composer-dependencies"><img src="https://agentmods.dev/badge/skills/krzysztofsurdy/code-virtuoso/composer-dependencies.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.00042 | $0.02663 |
| Opus 5.5 | $0.00017 | $0.01065 |
| Sonnet 5.5 | $0.00008 | $0.00533 |
| Haiku 4.5 | $0.00004 | $0.00266 |
Grade A, and why
composer-dependencies 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.
How it starts
The opening of the file, as written. The whole thing — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Composer Dependencies Update
Dependency updates are maintenance, not features. Do them regularly in small batches rather than rarely in large ones. Every update follows the same cycle: audit, update, verify, commit.
Core Principles
| Principle | Meaning |
|---|---|
| Changelog first | Before any major dependency update, search the web for the package's changelog or UPGRADE file, or ask the user for it. Never guess what changed |
| Security first | Run composer audit before and after every update. Vulnerabilities take priority over everything |
| Small batches | Update one package or one logical group at a time. Never update everything at once |
| Lock file is truth | Always commit composer.lock. Production uses composer install, never composer update |
| Verify before merging | Every update must pass the full test suite and static analysis before merging |
| Caret by default | Use ^ constraints for most dependencies. They balance stability with receiving fixes |
First step: read the changelog
Before updating any dependency to a new major version, you MUST obtain the actual changelog:
- Search the web for
{package-name} CHANGELOGor{package-name} UPGRADE guide(e.g.,doctrine/orm UPGRADE.md github) - Or ask the user to provide the changelog or release notes
- Check the package's GitHub repository for
CHANGELOG.md,UPGRADE.md, or release notes
This is required for major updates. Each package has its own breaking changes, and this skill cannot know them. For patch and minor updates, changelogs are recommended but do not block the update.
Update strategies by risk level
| Strategy | Scope | Risk | Frequency | Command |
|---|---|---|---|---|
| Patch only | Bug fixes (1.2.3 -> 1.2.4) | Lowest | Weekly | composer update --patch-only |
| Minor | New features, backward-compatible (1.2 -> 1.3) | Low | Biweekly | composer update --minor-only |
| Major | Breaking changes possible (1.x -> 2.0) | Highest | Planned, one at a time | composer update vendor/package --with-all-dependencies |
| Security | Vulnerability fixes | Urgent | Immediately | composer audit then targeted update |
What ships with it
2 files 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 Changed · +50 lines · -42 tokens per session 91f49560ac4d
- 1mo ago First seen · 174 lines · 84 tokens per session scan A 8f96e23d68d4
composer-dependencies is a skill published in the GitHub repository krzysztofsurdy/code-virtuoso (36 stars, last pushed yesterday), licensed MIT. It adds 42 tokens to every session and 2,663 once invoked, about $0.0002 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-30.
Other skills, from other repositories
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.
yao-geoflow-template
Use only for explicit legacy GEOFlow template skill questions, old PHP template-package contracts, or historical outputs using root index.php/article.php/category.php/archive.php and includes/.php. Route current Laravel Blade themes, reference-site cloning, homepage modules, leadform, theme editor, channel frontend…
loom-php
PHP language expertise for idiomatic, production-quality code.
phpunit-unit-test-reviewing
Internal sub-skill. Do not auto-activate. Use only when explicitly invoked by name by another skill or agent.
xml-config-migrating
Use this skill when a Shopware plugin or app-server extension needs its XML configuration migrated to PHP — phrases like "migrate services.xml", "convert my plugin config to PHP", "xml to php migration", "fix the XML deprecation", "prepare my plugin for Shopware 6.8 / Symfony 8", or when a deprecation like "The XML…
phpunit-integration-test-generation
Use this skill when the user asks to generate, write, or create integration tests for a Shopware 6 source class whose contract requires wired-up code — phrases like "generate integration tests for X", "write an integration test for this controller", "test this indexer", "create an integration test for the message…