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/z29k/notabeneWrote 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/z29k/notabene/claude-plugin)<a href="https://agentmods.dev/plugins/z29k/notabene/claude-plugin"><img src="https://agentmods.dev/badge/plugins/z29k/notabene/claude-plugin/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/z29k/notabene/claude-plugin"><img src="https://agentmods.dev/badge/plugins/z29k/notabene/claude-plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
notabene 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 4d 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": "notabene",
"version": "0.17.0",
"description": "Turnkey docs review: set up notabene on any repo — write the config, create the .notabene store, and start the review server via npx (no toolchain to install) — then run the human↔agent loop: process browser comments on your docs, apply the feedback, mark resolved, write the journal, and verify.",
"author": {
"name": "z29k"
},
"keywords": ["docs", "review", "comments", "setup", "onboarding", "authoring", "mermaid", "diagrams", "notabene"]
}
What it installs
The manifest is a name and a version. 3 skills, 5 commands travel with it, and installing the plugin installs all of them — 635 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.
- 4d ago Changed e2f078955d25
- 11d ago Changed 349d62e6f043
- 1mo ago First seen · 10 lines scan A e119801a846b
notabene is a plugin published in the GitHub repository z29k/notabene (5 stars, last pushed 5d 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
han-coding
Coding-facing skills for the Han suite: writing, reviewing, testing, investigating, and standardizing code. Home of the tdd skill, which drives a feature or behavior through a BDD-framed red-green-refactor loop with an enforced observed-failure gate, and the refactor skill, which restructures existing code without…
han-communication
Foundational communication plugin for the Han suite. Owns the canonical readability standard, the writing-voice profile, and the explanation standard for talking to a reader who will not implement the work, plus the readability-guidance skill that surfaces the first two into a calling skill's own context for in-voice…
han-research
Pre-planning knowledge-work skills for the Han suite: understanding a problem before anyone commits to a plan. Home of research (research an open-ended question and end at an adversarially-validated recommendation), gap-analysis (compare two artifacts and report what is missing, incomplete, or conflicting), and…
han-core
The shared foundation of the Han suite: the specialist agent roster the other plugins dispatch (adversarial reviewers, analysts, architects, investigators, and the plan synthesizer), the project-discovery skill with its project-scanner agent, and the canonical evidence and YAGNI rule files. The documentation skills…
han-documentation
Documentation skills for the Han suite: writing down what the team built and decided. Home of project-documentation (create and maintain documentation for features, systems, and components), architectural-decision-record (create, extract, or convert ADRs), and runbook (create or update a runbook for a single…
han-plugin-builder
Guidance and tooling for building Claude Code skills and plugins. Carries the full body of skill-authoring, agent-authoring, and plugin-configuration guidance, and an init step that vendors that guidance into any repo as a path-scoped rule index so contributors get the right guidance loaded for the file they are…