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.
/plugin marketplace add mshadmanrahman/pm-pilotnpx agentmods add plugins/mshadmanrahman/pm-pilot/tech-to-pmgit 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/tech-to-pm)<a href="https://agentmods.dev/plugins/mshadmanrahman/pm-pilot/tech-to-pm"><img src="https://agentmods.dev/badge/plugins/mshadmanrahman/pm-pilot/tech-to-pm.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
tech-to-pm 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 4d 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": "tech-to-pm",
"description": "Turns engineering docs (architecture refs, API docs, ADRs, runbooks) into structured code-free context that PMs and designers can actually use.",
"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": [
"documentation",
"technical-translation",
"onboarding",
"knowledge-base"
]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 125 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 4d ago First seen · 19 lines scan A 8a1286831d32
tech-to-pm is a plugin published in the GitHub repository mshadmanrahman/pm-pilot (19 stars, last pushed 13d 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
budgetclaw
Zero-key Claude Code cost tracking, per project and per branch. Budget caps with SIGTERM enforcement, reads your local /.claude session logs, and syncs to a hosted team dashboard (Goei).
agents-specialized-domains
Domain-specific expert agents for validation, knowledge-graph, and other specialized tasks.
gmgn-cli
9 GMGN skills — token info & security, holder chip analysis, K-line market data & trending tokens, wallet portfolio analysis, wallet copy-trade scoring, follow/KOL/Smart Money tracking, DEX swap execution, and launchpad token creation, and chart pattern reading on top of that market data.
pipefy
Pipefy workflow integration for Claude Code.
humanizer
Rewrite AI-sounding text so it reads naturally without changing what it says.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.