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/lfyxhappy/lfcode/pull-request-authornpx skills add lfyxhappy/lfcode --skill pull-request-authorgit clone --depth 1 https://github.com/lfyxhappy/lfcodeWrote 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/lfyxhappy/lfcode/pull-request-author)<a href="https://agentmods.dev/skills/lfyxhappy/lfcode/pull-request-author"><img src="https://agentmods.dev/badge/skills/lfyxhappy/lfcode/pull-request-author.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.1 | $0.00064 | $0.00322 |
| Opus 5 | $0.00032 | $0.00161 |
| Sonnet 5 | $0.00013 | $0.00064 |
| Haiku 4.5 | $0.00006 | $0.00032 |
Grade A, and why
pull-request-author 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 yesterday.
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
Pull Request Author
Make a change easy to review, validate, and safely merge.
Workflow
- Read repository contribution and pull-request templates, then inspect branch, upstream, worktree status, target base, and relevant diff.
- Confirm intended scope, included files, excluded user edits, migration or rollout implications, and the requested external Git actions.
- Run the repository's appropriate focused checks and collect concise evidence for behavior, UI, artifact, or migration validation.
- Draft a clear title and description covering motivation, behavior change, compatibility, tests, screenshots or recordings when required, and known follow-ups.
- Stage, commit, push, or open the pull request only after explicit approval and only for the reviewed scope.
Boundaries
- Do not stage unrelated work, force-push, rewrite shared history, or create a pull request from an unreviewed dirty worktree.
- Do not claim a pull request is ready when required checks, generated artifacts, or reviewer-visible evidence are missing.
- Never expose remote credentials, private URLs, or sensitive issue content.
Completion Check
Distinguish prepared, committed, pushed, and opened states. Report the final diff scope, validation, and any external action not performed.
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.
- yesterday First seen · 27 lines · 64 tokens per session scan A 8d4ed33d4dff
pull-request-author is a skill published in the GitHub repository lfyxhappy/lfcode (2 stars, last pushed 4d ago), licensed MIT. It adds 64 tokens to every session and 322 once invoked, about $0.0003 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-09-05.
Other skills, from other repositories
agentbro-pr-merge
Use when reviewing, fixing CI for, approving workflows for, or merging AgentBro pull requests into dev/main, especially external contributor PRs where contributor attribution matters.
open-code-review
Use Alibaba Open Code Review (ocr) to review git diffs, staged changes, branches, or scan a workspace, then summarize findings and optionally fix high-confidence issues.
Release Readiness
Review a change against release gates, rollback safety, validation evidence, and operational risk.
dcc-orchestration
Orchestrate Codex subagents for complex multi-part coding work. Use when independent exploration, review, tests, or bounded implementation streams can run in parallel; do not use for small sequential tasks or tightly coupled concurrent edits.
Review a GitHub PR (via gh)
Review a specific GitHub pull request with gh — fetch the diff, fan out reviewers, consolidate, and optionally post the review. Requires the gh CLI or the GitHub MCP server.
Implement (multi-agent loop)
Orchestrate an implement -> review -> fix loop with subagents until reviewers sign off.