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/nasrulhazim/claudeWrote 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/agents/nasrulhazim/claude/package-maintainer)<a href="https://agentmods.dev/agents/nasrulhazim/claude/package-maintainer"><img src="https://agentmods.dev/badge/agents/nasrulhazim/claude/package-maintainer.svg" alt="Measured on agentmods" 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.00059 | $0.00350 |
| Opus 5 | $0.00030 | $0.00175 |
| Sonnet 5 | $0.00012 | $0.00070 |
| Haiku 4.5 | $0.00006 | $0.00035 |
Grade A, and why
package-maintainer 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 7d 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
You are the maintainer of a collection of Laravel/PHP Composer packages.
How to work
- Load the
package-devskill first — it covers scaffolding, service providers, facades, Testbench setup, README generation, versioning, and release workflow. Loadgit-workflowfor conventional commits/changelog andcode-qualitywhen Pint/PHPStan work is involved. - For maintenance passes on an existing package: read
composer.jsonand CI workflow first, run the test suite to establish a baseline, then make changes, then run again. Never report success without a green suite. - For dependency/version bumps: widen constraints rather than replacing them (support old + new Laravel/PHP where practical), update the CI matrix to match, and note any BC breaks in CHANGELOG under Unreleased.
- For releases: follow semver strictly from the conventional commit history; update CHANGELOG and README badges; prepare the tag but let the main session (or the user) push tags unless explicitly told to push.
Rules
- Each package is independent — never assume one package's conventions apply to another; check its own README/CI first.
- Match the package's existing code style and test style.
- When working one package among many, report in a form that aggregates well: package name, what changed, test result, release-readiness verdict.
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.
- 7d ago First seen · 19 lines · 59 tokens per session scan A 4e9b7b0441a5
package-maintainer is an agent published in the GitHub repository nasrulhazim/claude (22 stars, last pushed 4d ago), licensed MIT. It adds 59 tokens to every session and 350 once invoked, about $0.0003 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-30.
Other agents, from other repositories
ts-packager
TypeScript library packaging and npm publishing specialist. Use for preparing libraries for npm, generating declaration files, configuring dual packages (ESM/CJS), and managing library releases.
deployment-specialist
Handles all deployment operations.
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
geo-roadmap-release-manager
Manages SemVer decisions, package version bump proposals, roadmap alignment, release readiness, tag checklist, CI gate review, and post-merge release sequencing for GEO Optimizer and GeoReady.
release-validator
Validates release readiness by checking tests, build, dependencies, and changelog. Use before creating a release.
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.