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/mshadmanrahman/pm-pilotWrote 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/plugins/mshadmanrahman/pm-pilot/pm-dev)<a href="https://agentmods.dev/plugins/mshadmanrahman/pm-pilot/pm-dev"><img src="https://agentmods.dev/badge/plugins/mshadmanrahman/pm-pilot/pm-dev/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/plugins/mshadmanrahman/pm-pilot/pm-dev"><img src="https://agentmods.dev/badge/plugins/mshadmanrahman/pm-pilot/pm-dev.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
pm-dev 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 1mo 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
{
"name": "pm-dev",
"description": "Shipping discipline for PMs who code: TDD workflow, pre-commit verification loop, security review, research-before-build.",
"version": "1.0.0",
"author": {
"name": "Shadman Rahman",
"url": "https://github.com/mshadmanrahman"
},
"homepage": "https://github.com/mshadmanrahman/pm-pilot",
"repository": "https://github.com/mshadmanrahman/pm-pilot",
"license": "MIT",
"keywords": [
"tdd",
"verification",
"security-review",
"code-quality"
]
}
What it installs
The manifest is a name and a version. 4 skills, 4 commands, 3 agents travel with it, and installing the plugin installs all of them — 199 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill security-review A 11 tokens
- Skill tdd-workflow A 18 tokens
- Skill search-first A 10 tokens
- Skill verification-loop A 18 tokens
- Command code-review A 14 tokens
- Command plan A 19 tokens
- Command tdd A 19 tokens
- Command verify A 15 tokens
- Agent tdd-guide A 29 tokens
- Agent build-error-resolver A 23 tokens
- Agent code-reviewer A 23 tokens
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.
- 1mo ago First seen · 19 lines scan A 50c62ab947fc
pm-dev is a plugin published in the GitHub repository mshadmanrahman/pm-pilot (22 stars, last pushed 17d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
backend-development
Backend API design, GraphQL architecture, workflow orchestration with Temporal, and test-driven backend development.
backend-development
Backend API design, GraphQL architecture, workflow orchestration with Temporal, and test-driven backend development.
code-quality
Code quality pipeline — SOLID refactoring, TDD workflow, design patterns, performance optimization, and 6 specialist review agents.
engineering
Engineering workflow skills, review agents, and a /feature pipeline: orientation, planning, test-driven development, systematic debugging, refactoring, error handling, observability, containers, CI pipelines, dependency upgrades, migration planning, incident postmortems, code review, completion verification, and…
harnessay
Profile Claude Code and Codex transcripts: context budget reports, before/after comparisons, source evidence, and skill regression tests. Local-only, stdlib-only.
aio-gherkin-refine
Comprehensive BDD field guide — writes and reviews Gherkin with expert quality. Includes Example Mapping, 3 Amigos, anti-patterns catalog, and declarative style guide.