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/alexmmatos/essentials-claude-codeWrote 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/alexmmatos/essentials-claude-code/platform-engineer)<a href="https://agentmods.dev/agents/alexmmatos/essentials-claude-code/platform-engineer"><img src="https://agentmods.dev/badge/agents/alexmmatos/essentials-claude-code/platform-engineer.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.00054 | $0.01454 |
| Opus 5 | $0.00027 | $0.00727 |
| Sonnet 5 | $0.00011 | $0.00291 |
| Haiku 4.5 | $0.00005 | $0.00145 |
Grade A, and why
platform-engineer 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 5d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 5d ago First seen · 287 lines · 54 tokens per session scan A ce8b56c64fb7
platform-engineer is an agent published in the GitHub repository alexmmatos/essentials-claude-code (1 stars, last pushed 2mo ago), with no licence file. It adds 54 tokens to every session and 1,454 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-09-03.
Other agents, from other repositories
product-manager
Converts feature asks into structured specifications with user stories, acceptance criteria, and scope boundaries.
the-program-manager
Use for multi-team, multi-month technical program management — dependency mapping across teams, risk gates per launch phase, adopting orphaned cross-team problems, designing rollout plans with go/no-go criteria, drafting status comms for different audiences, framing escalations. Trigger when the user is running a…
the-slo-designer
Use when a team needs to define reliability targets for a service — SLOs, error budgets, and the monitoring setup that makes those commitments real rather than aspirational. Trigger when the user says "what SLOs should we have for this?", "how do we set reliability targets?", "we need to define our error budget", or…
the-retro-facilitator
Use when facilitating a team retrospective or post-mortem after a project, incident, or sprint. Trigger for structured retros that produce action items, not just conversation. Distinct from the-incident-responder (real-time incident management) and the-postmortem-facilitator (blameless postmortem after infrastructure…
the-status-crafter
Use for recurring operational status reporting — weekly/monthly status updates, stakeholder updates, leadership reports on an ongoing workstream. Trigger phrases include "help me write my weekly status update", "draft a monthly report for leadership", "what should I put in my stakeholder update?", "status email that…
project-manager
Project delivery specialist. Invoke for sprint planning, delivery milestones, dependency mapping, RAID logs, status reports, retrospectives, and cross-functional execution coordination. Distinct from product-manager, use this for delivery and execution, not product discovery.