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/PackkitLabs/create-packkit-jsWrote 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/mcp/packkitlabs/create-packkit-js/create-packkit)<a href="https://agentmods.dev/mcp/packkitlabs/create-packkit-js/create-packkit"><img src="https://agentmods.dev/badge/mcp/packkitlabs/create-packkit-js/create-packkit/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/mcp/packkitlabs/create-packkit-js/create-packkit"><img src="https://agentmods.dev/badge/mcp/packkitlabs/create-packkit-js/create-packkit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
create-packkit 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
{ "create-packkit": { "command": "npx", "args": [ "-y", "create-packkit" ] } }
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 · 9 lines scan A 387f878bf4a9
create-packkit is an MCP server published in the GitHub repository PackkitLabs/create-packkit-js (1 stars, last pushed 5d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. 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 mcp servers, from other repositories
klaussy
MCP server "klaussy" as configured in steph-dove/klaussy-agents. Launched with klaussy-mcp. Needs 1 environment variable to run.
backgen
MCP server "backgen" as configured in IbrahimKhaled19/BackGen. Runs D:/Projects/BackGen/dist/mcp/index.js with node.
scalattice-cli
Scalattice CLI - session login, credits, fleet, OpenAI-compatible keys, MCP. Runs locally from the scalattice-cli npm package.
semver-checks
Detect breaking changes in your TypeScript library's public API and recommend the SemVer bump. Runs locally from the semver-checks npm package.
safe-audit-fix
Safely fix npm audit vulnerabilities: one fix at a time, test after each, auto-revert anything that breaks. Usable as a CLI or as an MCP server for AI assistants. Runs locally from the safe-audit-fix npm package.
blastradius
Dependency blast-radius analyzer: before you upgrade an npm package, see exactly which of YOUR files and functions touch its changed API surface. Runs locally from the @justfeltlikerunning/blastradius npm package.