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/ihudak/ihudak-claude-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/ihudak/ihudak-claude-plugins/guideline-reviewers)<a href="https://agentmods.dev/plugins/ihudak/ihudak-claude-plugins/guideline-reviewers"><img src="https://agentmods.dev/badge/plugins/ihudak/ihudak-claude-plugins/guideline-reviewers/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/ihudak/ihudak-claude-plugins/guideline-reviewers"><img src="https://agentmods.dev/badge/plugins/ihudak/ihudak-claude-plugins/guideline-reviewers.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
guideline-reviewers 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 yesterday.
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": "guideline-reviewers",
"version": "1.0.0",
"description": "Reviews an OpenAPI specification against bundled REST API and IAM permission-naming guidance, and reviews application code or UI against bundled public design-system and accessibility standards. Ships the guidance it reviews against — Google AIP, Zalando, Microsoft REST, OpenAPI 3.1 and ~20 RFCs for APIs; Apple HIG, Material Design 3, Microsoft Fluent 2, W3C WCAG 2.2, ARIA APG and NN/g for interfaces — plus a Spectral ruleset that runs against a spec directly. Standalone: it consumes no workflow artefact and produces none.",
"author": { "name": "Ivan Gudak", "email": "[email protected]" },
"homepage": "https://github.com/ihudak/ihudak-claude-plugins",
"repository": "https://github.com/ihudak/ihudak-claude-plugins",
"license": "MIT",
"keywords": ["openapi", "rest", "accessibility", "design-system", "review"]
}
What it installs
The manifest is a name and a version. 2 commands, 2 agents travel with it, and installing the plugin installs all of them — 278 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.
- yesterday First seen · 11 lines scan A 9fccafa089da
guideline-reviewers is a plugin published in the GitHub repository ihudak/ihudak-claude-plugins (2 stars, last pushed yesterday), 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-09.
Other plugins, from other repositories
renaissance-architecture
Software architecture and UI/UX principles for building genuinely new solutions through first-principles thinking, not derivative work.
better-auth
Skill for integrating Better Auth - comprehensive TypeScript authentication framework for Cloudflare D1, Next.js, Nuxt, and 15+ frameworks. Use when adding auth, encountering D1 adapter errors, or implementing OAuth/2FA/RBAC features.
cloudflare-queues
This skill should be used when the user asks to "set up Cloudflare Queues", "create a message queue", "implement queue consumer", "process background jobs", "configure queue retry logic", "publish messages to queue", "implement dead letter queue", or encountering "queue timeout", "message retry", "throughput exceeded".
cloudflare-r2
Cloudflare R2 S3-compatible object storage with SQL, Iceberg, event notifications, and automation. Use for buckets, uploads, CORS, presigned URLs, large files, S3 migration, analytics, or encountering R2ERROR, CORS failures, multipart issues.
api-changelog-versioning
Creates comprehensive API changelogs documenting breaking changes, deprecations, and migration strategies for API consumers. Use when managing API versions, communicating breaking changes, or creating upgrade guides.
api-contract-testing
Verifies API contracts between services using consumer-driven contracts, schema validation, and tools like Pact. Use when testing microservices communication, preventing breaking changes, or validating OpenAPI specifications.