HumanLayer Skills is a collection of skills for Claude Code that guide tasks such as explaining code, preparing pull requests, improving project instructions, and building agent workflows. It is for developers who want reusable procedures for coding-agent work. The catalogue entries are the project's own skills and plugins.
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/humanlayer/skillsWrote 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/humanlayer/skills/visual-pr)<a href="https://agentmods.dev/plugins/humanlayer/skills/visual-pr"><img src="https://agentmods.dev/badge/plugins/humanlayer/skills/visual-pr/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/humanlayer/skills/visual-pr"><img src="https://agentmods.dev/badge/plugins/humanlayer/skills/visual-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
visual-pr 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 28d 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": "visual-pr",
"description": "Create or update a pull request with a concise visual outline for reviewers",
"version": "1.0.0",
"author": {
"name": "humanlayer",
"email": "[email protected]"
},
"repository": "https://github.com/humanlayer/skills",
"license": "MIT",
"keywords": ["pull-request", "code-review", "visualization", "github", "claude-code"]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 15 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.
- 28d ago First seen · 13 lines scan A 19b30618fc3f
visual-pr is a plugin published in the GitHub repository humanlayer/skills (5,291 stars, last pushed 7d 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-18.
Other plugins, from other repositories
hunch
A git-native reasoning graph of decisions, bugs, and invariants for your codebase — queried and enforced at reasoning time. Adds the hunch MCP tools plus /hunch:capture, /hunch:heal, /hunch:why, /hunch:fix, /hunch:fragile.
aigon
aigon. Aigon is a local, open-source, spec-first software-delivery orchestrator for coding agents. It takes a Git-backed feature spec through isolated implementation, cross-agent review, and merge—using the agents and subscriptions you already have.
workflow
Code review and worktree workflow commands.
git
Git workflow tools: commits, PRs, review inbox, checkout, and work triage.
review-toolkit
Comprehensive PR review pipeline: a pre-review readiness gate (stops on merge conflicts or red code-related CI with a fix-it note, no verdict), branch-level analysis with merge-base attribution (the verdict is decided only by defects the diff introduced, worsened, or interacts with — purely pre-existing defects are…
ci-review
CI-optimized code review: multi-agent parallel review with confidence scoring and atomic GitHub PR review posting via gh api.