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/beava-dev/beava/beava-pr-reviewnpx skills add beava-dev/beava --skill beava-pr-reviewgit clone --depth 1 https://github.com/beava-dev/beavaWrote 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/beava-dev/beava/beava-pr-review)<a href="https://agentmods.dev/skills/beava-dev/beava/beava-pr-review"><img src="https://agentmods.dev/badge/skills/beava-dev/beava/beava-pr-review.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.00119 | $0.02275 |
| Opus 5 | $0.00060 | $0.01137 |
| Sonnet 5 | $0.00024 | $0.00455 |
| Haiku 4.5 | $0.00012 | $0.00228 |
Grade A, and why
beava-pr-review 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
beava-pr-review
Diff-aware code reviewer tuned for the beava codebase. Checks three
layers in order; surface findings sorted by severity (BLOCK > WARN > NIT)
with file:line anchors.
When to invoke
- User says "review this PR" / "PR review" / "audit this diff" / "check
for slop" against a feature branch or a PR URL on
beava-dev/beava. - After a substantial code change but before requesting
ok-to-testapproval — the local check.sh covers fmt/lint/test, this skill covers the human-judgment layer.
How to run
- Bound the diff.
git diff main...HEAD --stat(orgh pr diff <N> -R beava-dev/beavafor a remote PR). Read only the changed lines + ~30 lines of context per hunk. Do NOT review unchanged code. - Run automated gates first. Before LLM review, surface anything
the existing tools catch:
bash .github/scripts/check.sh --fast— fmt, clippy, ruff, mypy (advisory). If any FAIL, the PR is incomplete; tell the user to fix before requesting human review.
- Apply the three review layers below, in order. Skip a layer only if the diff doesn't touch its scope (e.g. skip "AI slop" for a pure .gitignore change).
- Emit the report in the format under "Output format" at the end.
Layer 1 — Real bugs
The most common categories worth checking against the diff:
- Off-by-one — index math, slice bounds, half-open vs closed
ranges. Especially in
crates/beava-core/src/agg_op.rs,crates/beava-runtime-core/src/router.rs, anywhere computingwindow_secs/bucket_secs. - Null / Option /
?propagation —.unwrap()in non-test code is WARN unless the PR shows the panic is provably unreachable.expect()with a useful message is fine. - Resource leaks — file descriptors, mio tokens, dropped futures (we hand-rolled the runtime; mio leaks don't auto-close like tokio).
- Concurrency — single-threaded apply is locked architecture
(
project_no_sharded_apply); any new thread / parallel iterator insidedispatch_*_syncis BLOCK. - Schema / wire compatibility — changes to
crates/beava-runtime-core/src/router.rsroutes,agg_op.rsAggKindvariants, orpython/beava/_app.py::_descriptor_to_nodewire shape break clients. WARN unless the PR body calls it out and ships a migration note. - TDD discipline (Phase 3+ only) — every plan task must produce a
test(...)commit before itsfeat(...)commit. Commits that showfeat:without a precedingtest:for the same scope are WARN (per CLAUDE.md §Conventions → TDD Discipline).
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 · 201 lines · 119 tokens per session scan A 625502a4710e
beava-pr-review is a skill published in the GitHub repository beava-dev/beava (138 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 119 tokens to every session and 2,275 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
update-docs
Update documentation pages to match source code changes on the current branch.
provider-research
Research every provider behind Pipecat's services for new models and API affordances, writing per-service reports and local branches for clear-cut updates; publishing is scripts/provider-watch/publish.py's job, run outside this skill.
cleanup
Review, refactor, document, and validate code changes in the current branch.
docstring
Document a Python module and its classes using Google style.
prose-review
Check that added comments, docstrings, and changelog entries document the code rather than narrate the change that produced it.
pr-description
Update a GitHub PR description with a summary of changes.