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 agentmods add skills/yaalalabs/agent-kernel/ak-dev-review-prnpx skills add yaalalabs/agent-kernel --skill ak-dev-review-prgit clone --depth 1 https://github.com/yaalalabs/agent-kernelWrote 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/yaalalabs/agent-kernel/ak-dev-review-pr)<a href="https://agentmods.dev/skills/yaalalabs/agent-kernel/ak-dev-review-pr"><img src="https://agentmods.dev/badge/skills/yaalalabs/agent-kernel/ak-dev-review-pr.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00129 | $0.04437 |
| Opus 5 | $0.00064 | $0.02218 |
| Sonnet 5 | $0.00026 | $0.00887 |
| Haiku 4.5 | $0.00013 | $0.00444 |
Grade A, and why
ak-dev-review-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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review a Pull Request Against Agent Kernel Practices
Use this skill when asked to review a specific pull request by number or URL. It fetches the PR with the GitHub CLI (gh), reviews the delta against Agent Kernel's documented practices, and pushes the verified findings to the PR as a single review with inline comments.
This skill is for reviewing someone else's PR, not for reviewing your own uncommitted working-tree changes.
Goal
Produce a thorough, low-noise review grounded in Agent Kernel's own standards — architecture, code quality, and testing skills — and publish it on the PR so the author can act on it, without duplicating feedback that is already on the PR.
Inputs
- PR identifier (required): a number (
342), a URL, orowner/repo#number. If only a number is given, resolve the repository from theoriginremote of the current checkout. - Optional scope hints: the requester may narrow the review ("focus on the session store changes") — honor them, but still flag anything clearly dangerous outside that scope.
If no PR identifier can be determined, stop and ask for one. Do not guess.
Step 1: Fetch the PR Context
Gather everything before forming opinions:
# Metadata: title, body, author, base/head, state, linked issues
gh pr view <N> --json number,title,body,author,baseRefName,headRefName,state,files,additions,deletions,url
# The full diff
gh pr diff <N>
# Existing discussion and review comments — needed for dedupe in Step 5
gh pr view <N> --comments
gh api repos/{owner}/{repo}/pulls/<N>/comments --paginate
# CI status
gh pr checks <N>
Then make the PR head readable locally without touching the developer's working tree:
git fetch origin pull/<N>/head:refs/remotes/pr/<N>
git show pr/<N>:<path> # read any file at the PR head
Never run gh pr checkout — it would switch the developer's branch.
Read the full content of every changed source file at the PR head, not just the diff hunks. A diff hunk without surrounding context is the main source of false-positive review comments.
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.
- 5d ago First seen · 248 lines · 129 tokens per session scan A e7e282be58a0
ak-dev-review-pr is a skill published in the GitHub repository yaalalabs/agent-kernel (166 stars, last pushed today), licensed Apache-2.0. It adds 129 tokens to every session and 4,437 once invoked, about $0.0006 per session on Opus 5. 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-30.
Other skills, from other repositories
notion
Notion workspace integration for searching pages, managing databases, creating postmortems, and exporting RCA findings.
datadog
Datadog monitoring integration for querying logs, metrics, monitors, events, traces, hosts, and incidents during RCA investigations.
scaleway
Scaleway cloud integration for managing instances, Kapsule Kubernetes clusters, object storage, and managed databases via CLI and Terraform.
isaac-automator
Deploy and operate a cloud Isaac Workstation with Isaac Automator: provision a GPU VM running Isaac Sim, Isaac Lab, and/or Isaac Lab Arena on AWS, GCP, Azure, or Alibaba Cloud, connect to it, move data in and out, control cost with stop/start, repair, import existing deployments, and destroy. Use when the user wants a…
bitbucket
Bitbucket code repository integration for managing repos, branches, PRs, issues, and CI/CD pipelines.
github
GitHub code repository integration for investigating code changes, deployments, commits, PRs, and suggesting fixes during RCA.