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/hmcts/agentic-plugins-marketplaceWrote 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/hmcts/agentic-plugins-marketplace/nodejs-project)<a href="https://agentmods.dev/plugins/hmcts/agentic-plugins-marketplace/nodejs-project"><img src="https://agentmods.dev/badge/plugins/hmcts/agentic-plugins-marketplace/nodejs-project.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
nodejs-project 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.
What it actually says
{
"name": "nodejs-project",
"version": "1.0.0",
"description": "CLAUDE.md template for Node.js/TypeScript projects using Vitest, ESLint, and Prettier",
"author": {
"name": "Agentic Plugins Marketplace",
"email": "[email protected]"
},
"license": "MIT",
"keywords": ["nodejs", "typescript", "vitest", "eslint", "prettier"]
}
What it installs
The manifest is a name and a version. 1 command travel with it, and installing the plugin installs all of them — 0 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.
- 2d ago First seen · 12 lines scan A 76827a4af1db
nodejs-project is a plugin published in the GitHub repository hmcts/agentic-plugins-marketplace (3 stars, last pushed 2d 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-09-05.
Other plugins, from other repositories
typescript-dev
TypeScript implementation, testing, and code review skills, deploys npm/vitest permissions via SessionStart hook.
js-ts
JavaScript and TypeScript development toolkit with ESLint, Vitest, and unit testing best practices.
biomejs--biome--testing-codegen
Guide for testing workflows and code generation commands in Biome. Use when running snapshot tests for lint rules, managing insta snapshots, or regenerating analyzer/parser/formatter code after changes.
tdd-ts
TypeScript quality tools: tsc, ESLint, Prettier, Jest/Vitest.
typescript-tdd-cookbook
TDD pattern cookbook for TypeScript development.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.