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.
npx skills add supatest-ai/alan-skills --skill alan-review-prgit clone --depth 1 https://github.com/supatest-ai/alan-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/skills/supatest-ai/alan-skills/alan-review-pr)<a href="https://agentmods.dev/skills/supatest-ai/alan-skills/alan-review-pr"><img src="https://agentmods.dev/badge/skills/supatest-ai/alan-skills/alan-review-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/skills/supatest-ai/alan-skills/alan-review-pr"><img src="https://agentmods.dev/badge/skills/supatest-ai/alan-skills/alan-review-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
- Snyk warn
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00017 | $0.02144 |
| Opus 5 | $0.00009 | $0.01072 |
| Sonnet 5 | $0.00003 | $0.00429 |
| Haiku 4.5 | $0.00002 | $0.00214 |
Grade C, and why
alan-review-pr scanned grade C with 2 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 11d 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.
Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
GitHub tokens, gh CLI auth, SSH keys, .netrc files, environment variables, or Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- `curl` or `wget` to api.github.com How it starts
The opening of the file, as written. The whole thing — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MANDATORY: Use Alan MCP Tools
The Alan MCP server provides GitHub tools that are ALREADY in your tool list.
They work exactly like Read, Bash, Edit — you call them as tool invocations.
They are named with the prefix mcp__alan__github_.
Authentication is handled automatically by the MCP server. You do NOT need GitHub tokens, gh CLI auth, SSH keys, .netrc files, environment variables, or any credentials. The tools work immediately with zero setup.
NEVER do any of the following for GitHub API access:
curlorwgetto api.github.comghCLI commands (gh pr, gh api, etc.)env | grepor scanning for tokens/secretscat ~/.netrc,git credential, orssh -T [email protected]- Any attempt to find, construct, or configure GitHub authentication
- Installing packages or CLIs for GitHub access
If an MCP tool call fails, report the error to the user. Do NOT fall back to CLI alternatives.
Verify tools are available
Before starting, confirm you can see mcp__alan__github_* tools in your
available tools. If they are NOT available, STOP and tell the user:
"The GitHub MCP tools are not available. Please check the sandbox MCP configuration."
Tool parameters
All GitHub PR tools require these parameters:
owner(string): GitHub org or username, e.g. "supatest-ai"repo(string): Repository name, e.g. "alan"prNumber(integer): PR number, e.g. 42
Example tool call:
Tool: mcp__alan__github_get_pull_request
Parameters: { "owner": "supatest-ai", "repo": "alan", "prNumber": 42 }
Resolving owner/repo
If the user only provides a PR number, run git remote get-url origin to get
the remote URL, then parse owner and repo from it. This is the ONLY git CLI
command you should run for GitHub operations. Everything else uses MCP tools.
Available GitHub MCP tools
| Tool name | Purpose |
|---|---|
mcp__alan__github_get_pull_request |
Get PR details (title, state, labels, merge status) |
mcp__alan__github_get_pr_diff |
Get unified diff of a PR |
mcp__alan__github_list_pr_comments |
List all comments on a PR |
mcp__alan__github_list_pr_reviews |
List all reviews on a PR |
mcp__alan__github_list_pr_files |
List changed files with additions/deletions |
mcp__alan__github_get_issue |
Get issue details |
mcp__alan__github_get_ci_status |
Get CI check run status for a ref |
mcp__alan__github_add_comment |
Add a comment to an issue or PR |
mcp__alan__github_create_pr_review |
Submit a review (APPROVE/REQUEST_CHANGES/COMMENT) |
mcp__alan__github_add_labels |
Add labels to an issue or PR |
mcp__alan__github_merge_pull_request |
Merge a PR |
mcp__alan__github_close_issue |
Close an issue or PR |
mcp__alan__github_request_reviewers |
Request reviewers on a PR |
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.
- 11d ago First seen · 226 lines · 17 tokens per session scan C ac45c49d550a
alan-review-pr is a skill published in the GitHub repository supatest-ai/alan-skills (0 stars, last pushed 22d ago), licensed Apache-2.0. It adds 17 tokens to every session and 2,144 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 2 findings (reaches for credential files, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.
Other skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…
oss-maintainer
Run an open-source project's issue/PR/release loop like a careful human maintainer — triage to root cause, absorb community PRs before duplicating them, gate every merge, ship honest releases, and thank the people doing your QA for free.