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/ejirocodes/agent-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/ejirocodes/agent-skills/nestjs)<a href="https://agentmods.dev/plugins/ejirocodes/agent-skills/nestjs"><img src="https://agentmods.dev/badge/plugins/ejirocodes/agent-skills/nestjs/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/ejirocodes/agent-skills/nestjs"><img src="https://agentmods.dev/badge/plugins/ejirocodes/agent-skills/nestjs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
nestjs-best-practices 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 1mo 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": "nestjs-best-practices",
"description": "NestJS 11+ best practices for enterprise Node.js applications with TypeScript.",
"version": "1.0.0",
"author": { "name": "ejirocodes" },
"license": "MIT"
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 185 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.
- 1mo ago First seen · 8 lines scan A 33eda5fabf9c
nestjs-best-practices is a plugin published in the GitHub repository ejirocodes/agent-skills (6 stars, last pushed 3mo 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
vovk
Claude Code plugin for Vovk.ts — topic-based skills covering segments, procedures, validation, SSR, and project setup.
bunjs
Bun and TypeScript toolkit. A /bunjs:bun index routes any task to the right one of eight task-shaped skills — setup, HTTP, errors, testing, security, production, performance, TUI — each shipping copyable code verified against Bun. Only Bun is tested.
kamae-ts
Kamae (構え) — an extensible harness of skill plugins for designing and implementing robust server-side TypeScript applications.
coding
Programming skills: Python, TypeScript, FastAPI, Postgres, coding guidelines, and more.
oas
Adaptive API code generator that learns your project patterns and syncs with OpenAPI specs.
elysia-skill
Expert knowledge for building type-safe web applications with ElysiaJS, including validation, lifecycle hooks, Eden end-to-end type safety, and integrations.