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 jaybocc2/dotfiles --skill code-reviewgit clone --depth 1 https://github.com/jaybocc2/dotfilesWrote 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/jaybocc2/dotfiles/code-review)<a href="https://agentmods.dev/skills/jaybocc2/dotfiles/code-review"><img src="https://agentmods.dev/badge/skills/jaybocc2/dotfiles/code-review/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/jaybocc2/dotfiles/code-review"><img src="https://agentmods.dev/badge/skills/jaybocc2/dotfiles/code-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00011 | $0.00375 |
| Opus 5.5 | $0.00004 | $0.00150 |
| Sonnet 5.5 | $0.00002 | $0.00075 |
| Haiku 4.5 | $0.00001 | $0.00038 |
Grade A, and why
code-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 1mo 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
If no issues are found:
Change summary: [Single sentence description of the overall change].
No issues found. Code looks clean and ready to merge.
If issues are found:
Change summary: [Single sentence description of the overall change].
[Optional general feedback for the entire change, e.g., unrelated change that should be in a different PR, or improved general approaches.]
File: path/to/file/one
L<LINE_NUMBER>: [] Single sentence summary of the issue.
More details about the issue, including why it is an issue (e.g., "This could lead to a null pointer exception").
Suggested change:
while (condition) {
unchanged line;
- remove this;
+ replace it with this;
+ and this;
but keep this the same;
}
L<LINE_NUMBER_2>: [MEDIUM] Summary of the next problem.
More details about this problem, including where else it occurs if applicable (e.g., "Also seen in lines L45, L67 of this file.").
File: path/to/file/two
L<LINE_NUMBER_3>: [HIGH] Summary of the issue in the next file.
Details...
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.
- 1mo ago First seen · 49 lines · 11 tokens per session scan A f9897dbfd874
code-review is a skill published in the GitHub repository jaybocc2/dotfiles (11 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 375 once invoked, about $0.0000 per session on Opus 5.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-09-02.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…