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 AcKeskin/contexture --skill pr-authorgit clone --depth 1 https://github.com/AcKeskin/contextureWrote 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/ackeskin/contexture/pr-author)<a href="https://agentmods.dev/skills/ackeskin/contexture/pr-author"><img src="https://agentmods.dev/badge/skills/ackeskin/contexture/pr-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.00080 | $0.01562 |
| Opus 5 | $0.00040 | $0.00781 |
| Sonnet 5 | $0.00016 | $0.00312 |
| Haiku 4.5 | $0.00008 | $0.00156 |
Grade A, and why
pr-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 3d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pr-author
Reviewee-side PR drafting. The second of the GitHub reviewee triad; siblings are pre-push and pr-triage.
PR title and body get composed in-place each time with varying quality — title length, summary structure, test plan, base branch all improvised. This skill drafts them to a contract, shows you the draft, and hands you a ready-to-run command. It does not open the PR itself.
No Claude-initiated GitHub writes (triad-wide boundary — see pre-push). This skill drafts the PR and produces the exact gh pr create command for the user to run. Claude never executes gh pr create. Read-only gh / git calls (resolving base, listing commits) run freely.
Auto-fires via this description, not a hook (per skill-auto-fire).
When to run
Auto-fire when:
- About to run
gh pr create(any form) — intercept and draft first. - Just after a successful first push (
git push -u origin <branch>) to a non-default branch that has no open PR (the pre-push handoff moment). - The user says "open a PR", "create the pull request", "let's PR this", or equivalent.
Skip when:
- The user says "draft only, don't post" — still draft the title/body and surface it, but don't produce the run-it prompt; just hand over the text.
- The current branch is the default branch (nothing to PR from).
Manual trigger: /pr-author.
Procedure
1. Resolve PR context
All read-only:
- Branch —
git rev-parse --abbrev-ref HEAD. - Base branch —
git symbolic-ref refs/remotes/origin/HEAD(striprefs/remotes/origin/); fall back tomain→master→trunkby checking which exists on the remote. - Fork case —
gh repo view --json parent. If the repo has a parent (the user is contributing via a fork), the base isupstream's default branch, notorigin's. Adjust and note it in the draft. - Commits in range —
git log <base>..HEAD --oneline. - Diff stats —
git diff --stat <base>..HEAD. - Linked issues — scan commit messages in range for
#NNNreferences.
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.
- 3d ago First seen · 95 lines · 80 tokens per session scan A 72b7f03e5f27
pr-author is a skill published in the GitHub repository AcKeskin/contexture (2 stars, last pushed 1mo ago), licensed MIT. It adds 80 tokens to every session and 1,562 once invoked, about $0.0004 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-03.
Other skills, from other repositories
core-workflow
Detailed development workflow patterns, checklists, and standards. Auto-loads for complex tasks, planning, debugging, testing, or when explicit patterns are needed. Contains session protocols, git conventions, security checklists, testing strategy, and communication standards.
debug-systematic
Systematic 4-phase debugging methodology for complex, intermittent, or mysterious issues. Use when investigating bugs, race conditions, or unexplained failures.
auto-claude
Autonomous multi-agent coding with git worktree isolation, QA validation, and memory. Use for complex features requiring autonomous implementation.
OCR Review-to-Approval Loop
Drive a PR to an approved code review by looping OCR's multi-agent review and address steps. Runs /ocr:review then /ocr:address repeatedly until the review verdict is APPROVE, then one final /ocr:address for leftover suggestions, posting every review and every address round to the GitHub PR as comments. Use when the…
audit-pr
Audit a whole PR against the delivery contract and return MERGE-READY or evidenced blockers with the full URL. Consumes the current review-change REVIEW-PASS receipt instead of re-running review axes; posts a SHA-bound ready comment; never edits or merges. Triggers: "audit-pr", "is this PR ready", "merge gate".
resolve-repository-state
Resolve an explicit Normalized Repository State contradiction. This is the sole writer allowed to update frozen repository facts or accepted decisions. Triggers: "resolve repository state", "resolve contradiction", "update a frozen repository fact".