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 marchatton/agent-skills --skill landprgit clone --depth 1 https://github.com/marchatton/agent-skillsWrote 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/marchatton/agent-skills/landpr)<a href="https://agentmods.dev/skills/marchatton/agent-skills/landpr"><img src="https://agentmods.dev/badge/skills/marchatton/agent-skills/landpr.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.00022 | $0.00737 |
| Opus 5 | $0.00011 | $0.00368 |
| Sonnet 5 | $0.00004 | $0.00147 |
| Haiku 4.5 | $0.00002 | $0.00074 |
Grade A, and why
landpr 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 7d 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
/landpr
Input
- PR:
<pr-number>
Do (end-to-end)
Goal: PR ends in GitHub state MERGED (never CLOSED). Use gh pr merge with --rebase or --squash.
- Repo clean:
git status. - Identify PR meta (author + head branch):
gh pr view <pr-number> --json number,title,author,headRefName,baseRefName --jq '{number,title,author:.author.login,head:.headRefName,base:.baseRefName}'contrib=$(gh pr view <pr-number> --json author --jq .author.login)head=$(gh pr view <pr-number> --json headRefName --jq .headRefName)
- Fast-forward base:
git checkout maingit pull --ff-only
- Create temp base branch from
main:git checkout -b temp/landpr-<pr-number>
- Check out PR branch locally:
gh pr checkout <pr-number>
- Rebase PR branch onto temp base:
git rebase temp/landpr-<pr-number>- fix conflicts; keep history tidy
- Fix + tests + changelog:
- implement fixes + add/adjust tests
- update
CHANGELOG.mdand mention#<pr-number>+@$contrib
- Pick merge strategy (if unclear, ask):
- Rebase: preserve commit history
- Squash: single clean commit
- Full gate (BEFORE commit):
pnpm lint && pnpm build && pnpm test
- Commit via
committer(include#<pr-number>+ contributor in commit message):
committer "fix: <summary> (#<pr-number>) (thanks @$contrib)" CHANGELOG.md <changed files>- capture
land_sha=$(git rev-parse HEAD)
- Push updated PR branch (rebase => usually needs force):
git push --force-with-lease
- Merge PR (must show MERGED on GitHub):
- Rebase:
gh pr merge <pr-number> --rebase - Squash:
gh pr merge <pr-number> --squash - Never
gh pr close
- Sync
main+ push:
git checkout maingit pull --ff-onlygit push
- Comment on PR with what we did + SHAs + thanks:
merge_sha=$(gh pr view <pr-number> --json mergeCommit --jq '.mergeCommit.oid')gh pr comment <pr-number> --body "Landed via temp rebase onto main.\n\n- Gate: pnpm lint && pnpm build && pnpm test\n- Land commit: $land_sha\n- Merge commit: $merge_sha\n\nThanks @$contrib!"
- Verify PR state ==
MERGED:
gh pr view <pr-number> --json state,mergedAt --jq '.state + \" @ \" + .mergedAt'
- Delete temp branch:
git branch -D temp/landpr-<pr-number>
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.
- 7d ago First seen · 57 lines · 22 tokens per session scan A efc342875d7f
landpr is a skill published in the GitHub repository marchatton/agent-skills (5 stars, last pushed 6mo ago), licensed MIT. It adds 22 tokens to every session and 737 once invoked, about $0.0001 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-31.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".