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/Ozzeron/prompt-packWrote 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/ozzeron/prompt-pack/minimal)<a href="https://agentmods.dev/plugins/ozzeron/prompt-pack/minimal"><img src="https://agentmods.dev/badge/plugins/ozzeron/prompt-pack/minimal/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/ozzeron/prompt-pack/minimal"><img src="https://agentmods.dev/badge/plugins/ozzeron/prompt-pack/minimal.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
minimal 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": "minimal",
"displayName": "Prompt Pack — Minimal",
"description": "Core discipline only: engineering principles, reuse-before-create, token discipline, handoff. The 4-skill foundation every other profile builds on.",
"source": "./",
"skills": [
"./prompts/meta/engineering-principles",
"./prompts/meta/reuse-before-create",
"./prompts/meta/token-discipline",
"./prompts/delivery/handoff"
],
"keywords": [
"discipline",
"dry",
"foundation"
]
}What it installs
The manifest is a name and a version. 4 skills travel with it, and installing the plugin installs all of them — 344 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside marketplace.json#minimal in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 17 lines scan A 524f2f7a97cd
minimal is a plugin published in the GitHub repository Ozzeron/prompt-pack (8 stars, last pushed 1mo 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-03.
Other plugins, from other repositories
superpowers-zh
A Chinese-language plugin containing 20 AI coding skills, including translated and original workflows, for several coding-agent tools. Its listed topics include testing-driven development, debugging, and development practices.
project-brain
Folder structure + collaboration protocol so AI sessions can resume project context after compaction or window switch. One brain/ folder, 5 core files (PROJECT/MAP/STATUS/DECISIONS/HANDOFF), and a topic taxonomy.
multi-cursor
Official Cursor SDK coding harness.
memex
Zettelkasten-based agent memory system with bidirectional links.
papi
Persistent project management inside your AI coding tool. PAPI plans what to build next, tracks every decision, and keeps projects coherent across sessions — so a new session starts where the last one left off instead of from nothing.
specops
Spec-driven development workflow - transforms ideas into structured specifications (requirements, design, tasks) before implementation.