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/Abhillashjadhav/AI-PM-essential-skillsWrote 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/abhillashjadhav/ai-pm-essential-skills/pm-tactical)<a href="https://agentmods.dev/plugins/abhillashjadhav/ai-pm-essential-skills/pm-tactical"><img src="https://agentmods.dev/badge/plugins/abhillashjadhav/ai-pm-essential-skills/pm-tactical/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/abhillashjadhav/ai-pm-essential-skills/pm-tactical"><img src="https://agentmods.dev/badge/plugins/abhillashjadhav/ai-pm-essential-skills/pm-tactical.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
pm-tactical 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 10d 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-tactical",
"version": "0.2.1",
"description": "Five tested skills that make a PM's daily Claude workflow cheaper, faster, and self-checking — now proactive by default: model-complexity-router (silently scores every task handoff, not just direct questions), builder-validator (frozen-spec self-QA, checklist frozen silently, never invents gate-critical facts), prompt-optimizer-loop (one-mutation-per-round prompt tuning), cli-over-mcp-auditor (silent first-prompt relevance check plus full deep-audit flow), pm-context-system (observes the session and proposes one-line log entries instead of interviewing up front).",
"author": {
"name": "Abhillash Jadhav",
"url": "https://github.com/Abhillashjadhav"
},
"keywords": ["product-management", "ai-pm", "evals", "model-routing", "context-engineering"]
}
What it installs
The manifest is a name and a version. 5 skills, 3 agents travel with it, and installing the plugin installs all of them — 992 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.
- 10d ago First seen · 11 lines scan A df80b453409b
pm-tactical is a plugin published in the GitHub repository Abhillashjadhav/AI-PM-essential-skills (2 stars, last pushed 9d 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-31.
Other plugins, from other repositories
make-scenario-builder
Create Make.com (Integromat) scenarios with AI assistance - visual automation design.
bounty-board
Turns your repo's tech debt into an aging bounty economy. A SessionStart hook scans tracked files and prices each TODO/FIXME/HACK/skip as a wanted-poster bounty whose XP grows with its git-blame age, injects the top 3 as opportunistic side quests, and, via a PostToolUse hook, verifies and pays out bounties that…
standup-autopilot
Turns what your agents ACTUALLY did into a standup: captured from session transcripts (not commits/tickets, which miss uncommitted work, real test exit codes, and unresolved errors) and rolled up cross-repo. Stop/SessionEnd snapshot each session's outcome (task, branch + diffstat, tests + exit codes, PRs, blockers) to.
junior-flow
Helps junior developers create technical story markdown from a story tracker.
super-fr-dispatch
super-fr dispatch: queue phases to autonomous runners (VibeKanban adapter included) with per-PR quality gates.
dev-day
The complete developer day-loop for Claude Code + Jira: /start-session boots a senior-collaborator session (feedback memory, Jira backlog, standing plan-gate), /standup answers 'anything pending?', /bug-triage root-causes tickets, /groom preps them for estimation, /create-ticket files them, /jira-comment posts clean…