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/dalehurley/php-mcp-sdkWrote 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/dalehurley/php-mcp-sdk/changelog-maintenance)<a href="https://agentmods.dev/rules/dalehurley/php-mcp-sdk/changelog-maintenance"><img src="https://agentmods.dev/badge/rules/dalehurley/php-mcp-sdk/changelog-maintenance.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.00493 | $0.00493 |
| Opus 5 | $0.00246 | $0.00246 |
| Sonnet 5 | $0.00099 | $0.00099 |
| Haiku 4.5 | $0.00049 | $0.00049 |
Grade A, and why
changelog-maintenance 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 8d 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.
Changelog Maintenance Requirements
IMPORTANT: Always Review and Update the Changelog
The CHANGELOG.md file must be maintained for every change to the PHP MCP SDK.
Before Starting Any Work
-
Review the changelog to understand:
- Recent changes that might affect your work
- Current version and unreleased changes
- Any deprecated features to avoid using
-
Check for conflicts with ongoing work listed in "Unreleased"
After Completing Changes
-
Update the changelog immediately with:
- Clear description of what changed
- Category (Added/Changed/Deprecated/Removed/Fixed/Security)
- Any breaking changes or migration notes
- Dependencies added or updated
-
Format entries properly:
### Added - Brief description of new feature or capability - Another new feature with explanation if needed ### Changed - What was modified and why (if not obvious) ### Fixed - Bug that was fixed with issue reference if applicable
Changelog Update Checklist
When making changes, ensure the changelog includes:
- All new features or capabilities added
- Any changes to existing functionality
- Bug fixes with clear descriptions
- New dependencies or dependency updates
- Breaking changes highlighted with migration notes
- Security fixes (if applicable)
- Deprecation notices for features being phased out
Examples of Good Changelog Entries
✅ Good: "Added McpServer::registerBatchTools() method to register multiple tools at once, improving initialization performance"
❌ Bad: "Updated server code"
✅ Good: "Fixed memory leak in StdioTransport when handling messages larger than 1MB"
❌ Bad: "Fixed bug"
Remember
- The changelog is for humans, not machines - write clearly
- Include the "why" when the reason isn't obvious
- Group related changes together
- Keep entries concise but informative
- Update immediately after changes to avoid forgetting details
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.
- 8d ago First seen · 78 lines · 493 tokens per session scan A 7821ffcf422a
changelog-maintenance is a cursor rule published in the GitHub repository dalehurley/php-mcp-sdk (27 stars, last pushed 9mo ago), licensed MIT. It adds 493 tokens to every session, about $0.0025 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 cursor rules, from other repositories
versioning
Guidelines for library versioning.
atelier
Atelier UI/UX and Backend Architecture Quality Gate.
langfuse-mcp-general-rules
Cursor rule "langfuse-mcp-general-rules" from avivsinai/langfuse-mcp, covering building and publishing to pypi, version numbering and tagging and build and publish workflow.
release-gate
Release & deploy gate for @kadam-net/mcp-server — what the agent may do autonomously vs. what requires explicit human approval. Applies to all branch/MR/release/deploy work in this repo.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.