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/dryvist/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/dryvist/claude-code-plugins/project-standards)<a href="https://agentmods.dev/plugins/dryvist/claude-code-plugins/project-standards"><img src="https://agentmods.dev/badge/plugins/dryvist/claude-code-plugins/project-standards/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/dryvist/claude-code-plugins/project-standards"><img src="https://agentmods.dev/badge/plugins/dryvist/claude-code-plugins/project-standards.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
project-standards 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 8d 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": "project-standards",
"version": "6.3.0",
"description": "Claude skill authoring standards, workspace management, and skills/tools registry lookup",
"author": {
"name": "JacobPEvans"
},
"license": "MIT",
"repository": "https://github.com/JacobPEvans/claude-code-plugins",
"keywords": [
"claude",
"authoring",
"workspace",
"skills",
"registry",
"standards"
],
"skills": [
"./skills/claude-skill-authoring",
"./skills/workspace-standards",
"./skills/skills-registry",
"./skills/nix-tool-policy"
]
}
What it installs
The manifest is a name and a version. 4 skills travel with it, and installing the plugin installs all of them — 148 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.
- 8d ago Changed f6dc9f8af0b8
- 1mo ago Changed 6ffaab55fda7
- 1mo ago Changed 249552ada6e9
- 1mo ago Changed 5fc97fce4dd9
- 1mo ago Changed ed8e78a184ae
- 1mo ago First seen · 25 lines scan A 9e93505fb73c
project-standards is a plugin published in the GitHub repository dryvist/claude-code-plugins (3 stars, last pushed 3d ago), licensed Apache-2.0. 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-04.
Other plugins, from other repositories
standup-autopilot
Turns what your agents ACTUALLY did into a standup: captured from session transcripts (not commits/tickets, which miss uncommitted work, real test exit codes, and unresolved errors) and rolled up cross-repo. Stop/SessionEnd snapshot each session's outcome (task, branch + diffstat, tests + exit codes, PRs, blockers) to.
bounty-board
Turns your repo's tech debt into an aging bounty economy. A SessionStart hook scans tracked files and prices each TODO/FIXME/HACK/skip as a wanted-poster bounty whose XP grows with its git-blame age, injects the top 3 as opportunistic side quests, and, via a PostToolUse hook, verifies and pays out bounties that…
moai-pm
A project-starting hub for Claude Cowork that interviews you about the work, reviews installed add-ons, and creates project-specific instructions, agents, and workflows. It is intended to help both developers and non-developers set up a project.
gh-tools
GitHub workflow automation: GFM link validation, WebFetch enforcement, issue management, fork intelligence.
studio-engine-core
Core creation pipeline: onboard, create, fill, validate, test, package, publish — guided product creation with 20 structural quality patterns.
navigator
Finish What You Start - Sessions that last, AI that learns, Features that ship. Context engineering + Theory of Mind + Knowledge Graph + Loop Mode + Task Mode. Features Project Knowledge Graph (unified search, experiential memory), unified workflow orchestration, auto-update on session start, ToM-based verification…