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 RealManage/dx-trainingnpx agentmods add plugins/realmanage/dx-training/pm-toolkitgit clone --depth 1 https://github.com/RealManage/dx-trainingGrade A, and why
pm-toolkit 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 2d 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.
- 2d ago First seen · 17 lines scan A 57c69b362f60
pm-toolkit is a plugin published in the GitHub repository RealManage/dx-training (10 stars, last pushed 1mo ago), with no licence file. 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
workflow
Session workflow helpers and deferred-work backlog - knowledge capture, confusion handling, course correction, clipboard copy, backlog items.
contract-testing-flywheel
Generates a structured onboarding backlog that takes a team from zero to publishing verified consumer and provider contract tests on PactFlow — in Jira, GitHub Issues/Projects, or Azure DevOps, or as a manual markdown export. Modelled on the Contract Testing Flywheel: Planning → Requirements → Design → Implementation…
bottle
Bootstrap a project with a small, file-based documentation system so Claude Code keeps context, lessons, and decisions across session restarts instead of starting cold every time.
shiploop
Single-plugin marketplace for shiploop — a self-improving multi-agent harness (every resolved ticket writes a lesson into your git-tracked CLAUDE.md) that grinds your ticket backlog across every repo in your product.
shiploop
Self-improving multi-agent harness that grinds your ticket backlog across every repo in your product — guarded auto-merge on green CI, and every resolved ticket writes a lesson into your git-tracked CLAUDE.md. Every ticket starts on a cheap tier and escalates once, on measured failure, instead of being predicted…
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…