Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/stefaniuk/loadoutnpx agentmods add commands/stefaniuk/loadout/util.gh-pr-contentWrote 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/commands/stefaniuk/loadout/util.gh-pr-content)<a href="https://agentmods.dev/commands/stefaniuk/loadout/util.gh-pr-content"><img src="https://agentmods.dev/badge/commands/stefaniuk/loadout/util.gh-pr-content/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/commands/stefaniuk/loadout/util.gh-pr-content"><img src="https://agentmods.dev/badge/commands/stefaniuk/loadout/util.gh-pr-content.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.00009 | $0.03200 |
| Opus 5.5 | $0.00004 | $0.01280 |
| Sonnet 5.5 | $0.00002 | $0.00640 |
| Haiku 4.5 | $0.00001 | $0.00320 |
Grade A, and why
util.gh-pr-content 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.
How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mandatory preparation:
- Read the constitution and honour its non-negotiable rules.
- Read the Pull Request template at pull_request_template.md. This file is the single source of truth for the output structure; you must reproduce it verbatim (see Output requirements) and never paraphrase or hard-code a copy of it.
- Read the technology-specific instructions only for languages actually touched on this branch (look at the stat in the report; do not preload every instruction file). For example python.instructions.md, shell.instructions.md, makefile.instructions.md.
- Review the design context under
.copilot/analysis/only when it materially helps describe affected components.
Goal 🎯
Craft a diff-driven pull request title and body, ready to copy/paste, that compares the current branch against its detected base branch (not assumed to be main), summarises behaviour, lists verification evidence, and fills every section of pull_request_template.md.
Scope policy (non-negotiable) 🎯
The base branch is never assumed to be main. It is detected automatically (see §A) from the PR's actual base ref, or the repository's default branch, falling back to main only if neither can be determined. Everywhere below, "base branch" or "<base>" refers to this detected ref.
This section describes evidence precedence only, it does not instruct you to run anything. The single sanctioned command runs once in §A; everything named below is a description of a block already present in the resulting report.
A PR description covers the committed changes between the base branch and HEAD, plus any staged work when the current branch is the PR head branch. Unstaged working-tree changes are deliberately excluded. Evidence precedence is:
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 · 136 lines · 9 tokens per session scan A e617e0c7e179
util.gh-pr-content is a command published in the GitHub repository stefaniuk/loadout (1 stars, last pushed 13d ago), licensed MIT. It adds 9 tokens to every session and 3,200 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-12.
Other commands, from other repositories
sddp-implement
Command description: Implement the current feature tasks. Argument hint: [optional: phase or task to start from] Command category: feature-delivery Prerequisites: spec, plan, tasks, checklists:complete-if-present.
sddp-implement-qc-loop
Command description: Run implement and QC in a continuous loop. Argument hint: [optional: feature directory or branch name] Command category: orchestration Prerequisites: spec, plan, tasks.
sddp-plan
Command description: Create an implementation plan from the current feature specification. Argument hint: [optional: planning constraints or focus areas] Command category: feature-delivery Prerequisites: spec.
sddp-prd
Command description: Create or refine the canonical product document. Argument hint: [rough product idea, users, domain, or market opportunity] Command category: project-bootstrap Prerequisites: none.
sddp-qc
Command description: Run quality control against the implemented feature. Argument hint: [optional: testing focus such as unit tests, security audit, requirements sync] Command category: feature-delivery Prerequisites: spec, plan, tasks, implementation:complete.
sddp-specify
Command description: Create a feature specification from a feature description. Argument hint: [feature description] Command category: feature-delivery Prerequisites: project-instructions.