composer-tooling

composer-tooling is a skill for Claude Code from AratKruglik/claude-sdlc. It costs 177 tokens per session (1,204 once invoked), scanned A, original, MIT.

A guide to Composer, PHP's dependency manager and autoloader. It covers package versions, PSR-4 namespace mapping, scripts, platform requirements, and lockfiles.

In plain words
What is it for?
Use it to inspect or edit `composer.json`, manage dependencies, configure autoloading, run project scripts, and understand `composer.lock`.
Why use it?
It helps keep installed dependencies reproducible and prevents code from using PHP features that the project does not support.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Part of the php-foundation plugin — 3 skills shipped together

Good fit Use it to inspect or edit composer.json, manage dependencies, configure autoloading, run project scripts, and understand composer.lock.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/aratkruglik/claude-sdlc/composer-tooling
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.

Any agent
npx skills add AratKruglik/claude-sdlc --skill composer-tooling
Clone the repo
git clone --depth 1 https://github.com/AratKruglik/claude-sdlc

Made for: Claude Code.

Or install php-foundation, the plugin that ships this one along with the rest of its 3 skills.

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 composer-tooling

README.md
[![agentmods](https://agentmods.dev/badge/skills/aratkruglik/claude-sdlc/composer-tooling/github.svg)](https://agentmods.dev/skills/aratkruglik/claude-sdlc/composer-tooling)
Your own site
<a href="https://agentmods.dev/skills/aratkruglik/claude-sdlc/composer-tooling"><img src="https://agentmods.dev/badge/skills/aratkruglik/claude-sdlc/composer-tooling/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.

agentmods 80×15 button for composer-tooling

Your own site · 80×15
<a href="https://agentmods.dev/skills/aratkruglik/claude-sdlc/composer-tooling"><img src="https://agentmods.dev/badge/skills/aratkruglik/claude-sdlc/composer-tooling.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 177 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,204 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found 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.1 $0.00177 $0.01204
Opus 5.5 $0.00071 $0.00482
Sonnet 5.5 $0.00035 $0.00241
Haiku 4.5 $0.00018 $0.00120

Measured 29d ago against content hash 731fb9ca6e20, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

composer-tooling 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 29d 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.

plugins/php-foundation/skills/composer-tooling/SKILL.md · 126 lines

How it starts

The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Composer Tooling (stack-agnostic)

Composer is the dependency manager and autoloader entry point for every modern PHP project. Read composer.json before doing anything else — it tells you the PHP version, the framework, and the available packages.

Project detection

cat composer.json                 # PHP version (require.php), framework, scripts
test -f composer.lock && echo "locked"   # lockfile present → reproducible installs

Key fields to read:

  • require.php — minimum PHP version (drives which language features you may use).
  • require — runtime dependencies; the framework marker lives here (laravel/framework, symfony/framework-bundle).
  • require-dev — dev/test tooling (phpunit, pest, phpstan, pint, php-cs-fixer).
  • autoload.psr-4 — namespace → directory map.
  • config.platform.php — pins the version the resolver targets (may differ from the runtime PHP).

composer.json vs composer.lock

  • composer.json declares intent — version ranges you accept.
  • composer.lock records the exact resolved versions. It is committed and is the source of truth for composer install.
Command Effect
composer install Installs the exact versions from composer.lock. Use in CI/deploy.
composer update <pkg> Re-resolves the named package, rewrites the lock. Use deliberately.
composer require <pkg> Adds to composer.json + updates the lock for that package.
composer require --dev <pkg> Same, into require-dev.

Never hand-edit composer.lock. Never run a bare composer update (updates everything) as part of a focused feature change.

Version constraints

{
  "require": {
    "php": "^8.2",              // >=8.2.0 <9.0.0 — recommended for libraries/apps
    "guzzlehttp/guzzle": "^7.8" // caret: compatible up to the next major
  }
}
  • Caret ^7.8 — allows >=7.8.0 <8.0.0. The default; respects SemVer.
  • Tilde ~7.8.0 — allows >=7.8.0 <7.9.0. Tighter; use when you must pin to a minor.
  • Exact 7.8.3 — avoid except to work around a specific broken release.
  • Avoid * and unbounded >= — they break reproducibility.

Read the full file on GitHub · 126 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. 29d ago Changed · +2 lines 731fb9ca6e20
  2. 1mo ago First seen · 124 lines · 177 tokens per session scan A 2d9b2f5dd9ff

Subscribe to this mod's changes

composer-tooling is a skill published in the GitHub repository AratKruglik/claude-sdlc (43 stars, last pushed 4d ago), licensed MIT. It adds 177 tokens to every session and 1,204 once invoked, about $0.0007 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-09-03.

Related

Other skills, from other repositories