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/a8cteam51/claude-code-pluginsWrote 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/a8cteam51/claude-code-plugins/page-annotator)<a href="https://agentmods.dev/plugins/a8cteam51/claude-code-plugins/page-annotator"><img src="https://agentmods.dev/badge/plugins/a8cteam51/claude-code-plugins/page-annotator/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/a8cteam51/claude-code-plugins/page-annotator"><img src="https://agentmods.dev/badge/plugins/a8cteam51/claude-code-plugins/page-annotator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
page-annotator 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": "page-annotator",
"version": "0.3.0",
"description": "Annotate the web page you're viewing in Chrome and file each note as a GitHub issue. An overlay installed as a Tampermonkey userscript lets you name a repository, click elements and leave notes; hit Create GitHub issues — Claude screenshots each annotated element and opens one issue per note, with the screenshot, selector, markup and browser details attached.",
"author": {
"name": "Automattic Special Projects"
},
"repository": "https://github.com/a8cteam51/claude-code-plugins",
"license": "MIT",
"keywords": [
"annotation",
"bug-report",
"browser",
"chrome",
"claude-in-chrome",
"design-review",
"front-end",
"github",
"issues",
"overlay",
"qa",
"screenshot",
"tampermonkey",
"userscript"
]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 160 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 · 27 lines scan A bf68cdaaf51b
page-annotator is a plugin published in the GitHub repository a8cteam51/claude-code-plugins (5 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-08-31.
Other plugins, from other repositories
claude-craft
Multi-stack framework for Claude Code teams: 12 stacks, BMAD v6 sprint workflow, browser QA automation, and Kanban — for tech leads adopting Claude Code with their team.
daily-working
End-to-end pipeline: pull a task from the project's task tracker (Redmine today) by ID, implement it with the Claude CLI, verify the result in a real browser via the claude-in-chrome extension, and keep the tracker ticket in sync throughout.
LUXOR Specialized Tools
Specialized developer tools including Playwright, Linear, asyncio patterns, unix-goto, and Pydantic.
before-you-build
Pre-build product risk review for founders, product teams, and AI-assisted builders before implementation starts.
kernel-sdks
TypeScript and Python SDK skills for building browser automation with Kernel's Typescript and Python SDKs.
obw
Obsidian Workspace — project-scoped vault productivity (capture / notes / PM). Skills own folder layout and templates; /obw:pm splits a spec into blocking tickets; /issue is a Claude Mod pane that lists a view of the project's dashboard, draws Mermaid as text diagrams, and can open a card in the browser through viz.…