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 microsoft/apmnpx agentmods add plugins/microsoft/apm/mock-claude-plugingit clone --depth 1 https://github.com/microsoft/apmGrade A, and why
mock-claude-plugin 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 yesterday.
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": "Mock Marketplace Plugin",
"version": "1.0.0",
"description": "A test marketplace plugin for APM integration testing",
"author": {"name": "APM Test Suite"},
"license": "MIT",
"repository": "microsoft/apm-test-plugin",
"homepage": "https://github.com/microsoft/apm",
"tags": ["testing", "example", "marketplace"],
"dependencies": []
}
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.
- yesterday First seen · 12 lines scan A 3bc51161f8ad
mock-claude-plugin is a plugin published in the GitHub repository microsoft/apm (3,668 stars, last pushed yesterday), 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
vibeflow
Spec-driven development for AI agents. Define what to build, let the agent build it right. Vibeflow separates thinking from coding with specs, guardrails, and audits — grounded in your project's real patterns.
rp1-base
Core knowledge management, documentation generation, and strategic analysis for Claude Code.
supply-chain-risk-auditor
Audit a project's npm, PyPI, and Go dependencies for supply-chain risk: version-matched advisories for direct dependencies and the full lockfile tree, abandoned upstreams, npm publisher concentration, and install scripts.
insecure-defaults
Detects insecure default configurations including hardcoded credentials, fallback secrets, weak authentication defaults, and dangerous values in production.
sharp-edges
Identify error-prone APIs, dangerous configurations, and footgun designs that enable security mistakes.
wisci
WISCI context engineering framework — Write, Isolate, Select, Compress, Iterate. Staleness-tracked context store (.wisci/), per-stream handoffs with a derived index, proactive session hooks, and context-enriched commits.