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 lootlog/monorepo --skill pull-requestsgit clone --depth 1 https://github.com/lootlog/monorepoWrote 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/lootlog/monorepo/pull-requests)<a href="https://agentmods.dev/skills/lootlog/monorepo/pull-requests"><img src="https://agentmods.dev/badge/skills/lootlog/monorepo/pull-requests/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/lootlog/monorepo/pull-requests"><img src="https://agentmods.dev/badge/skills/lootlog/monorepo/pull-requests.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00034 | $0.00617 |
| Opus 5.5 | $0.00014 | $0.00247 |
| Sonnet 5.5 | $0.00007 | $0.00123 |
| Haiku 4.5 | $0.00003 | $0.00062 |
Grade A, and why
pull-requests 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 today.
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.
This is a copy
100% identical to pull-requests — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
A pull request is ready when its tests, implementation, comments, and changeset are each the simplest that cover the intended behavior. Draft PRs can be used earlier; finishing means making the PR ready for review.
Workflow
Run each step in a fresh-context subagent when available; otherwise run it yourself. Pass along the task context and prior results so each step can check its gate.
- Keep tests focused. Read test-development for test placement and type. Cover each intended behavior once, in the existing test file for the module. For changes needing no tests, record why. Continue when removing any remaining case would leave intended behavior uncovered, or no tests are needed.
- Simplify the implementation. With the tests passing, look for a simpler or more idiomatic version: reuse helpers and patterns from nearby source and effect-development, and remove debugging code, scaffolding, and changes unrelated to the task. Continue when applicable targeted tests pass and every hunk in the diff from the merge base is required by the task.
- Review the full diff from the merge base as a maintainer would: correctness, failure and interruption paths, resource cleanup, naming and API consistency with neighboring modules, and documentation. Fix findings and review again. Continue when a review pass produces no findings.
- Clean up. Remove comments that restate code or narrate the change; keep the rest short and about why. Finalize the changeset with changesets. Continue when comments explain only what code cannot, and the changeset describes the final consumer impact or the no-changeset reason is recorded.
- Run the validation in the AGENTS.md validation table for each change type in the diff. Fix failures caused by the change; if fixes alter the diff, repeat the affected passes. Continue when applicable checks pass or commands that cannot run and their blockers are recorded.
- Open or update the pull request. Title: a short imperative summary.
Description: the problem addressed, notable decisions, and
Closes #<issue>for each GitHub issue resolved. Do not narrate the diff. Mark the PR ready for review. Continue when the final changes are pushed, the description matches the final diff, and the PR is ready for review.
The task is complete when each step's gate holds, validation has passed or been reported as not runnable with reasons, and the pull request is ready for review with a description matching the final diff.
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.
- today First seen · 51 lines · 34 tokens per session scan A d291556d75a7
pull-requests is a skill published in the GitHub repository lootlog/monorepo (29 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 617 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to pull-requests, differing in 0 lines, and is treated as a copy.
pull-requests compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| pull-requestslootlog/monorepo | Skill | 29 | yesterday | MIT | A | 34 | Claude Code, Codex |
| prYeachan-Heo/oh-my-claudecode | Skill | 41k | yesterday | MIT | A | 47 | Claude Code |
| otto-pr-review-loopomnigent-ai/omnigent | Skill | 11k | yesterday | Apache-2.0 | A | 17 | Claude Code, Codex |
| engram-branch-prGentleman-Programming/engram | Skill | 7.8k | yesterday | MIT | A | 37 | Claude Code, Codex |
| github-contributordaymade/claude-code-skills | Skill | 1.5k | yesterday | MIT | A | 105 | Claude Code, Codex |
| revdiffumputun/revdiff | Skill | 945 | yesterday | MIT | A | 250 | Claude Code |
| pr-description-writermohitagw15856/pm-claude-skills | Skill | 1.5k | yesterday | MIT | A | 80 | Claude Code, Codex |