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/module-federation/core/gh-pr-metadatanpx skills add module-federation/core --skill gh-pr-metadatagit clone --depth 1 https://github.com/module-federation/coreWrote 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/module-federation/core/gh-pr-metadata)<a href="https://agentmods.dev/skills/module-federation/core/gh-pr-metadata"><img src="https://agentmods.dev/badge/skills/module-federation/core/gh-pr-metadata.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 | $0.00086 | $0.00939 |
| Opus 5 | $0.00043 | $0.00469 |
| Sonnet 5 | $0.00017 | $0.00188 |
| Haiku 4.5 | $0.00009 | $0.00094 |
Grade A, and why
gh-pr-metadata 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GH PR Metadata
Overview
Normalize the current branch's GitHub PR metadata to this repo's expectations. Keep the title in conventional-commit style, keep the body aligned to .github/pull_request_template.md, and validate before handoff.
Ground the PR metadata in the live branch state, not stale branch names or old commit subjects. Always inspect the current branch diff versus its base before rewriting the PR title/body.
Read references/repo-pr-format.md when you need the exact section order, checklist items, or a title example.
Workflow
- Resolve the current branch PR.
gh pr view --json number,title,body,url,headRefName,baseRefName
- Inspect the current branch state against the PR base branch.
At minimum, check:
git diff --name-status origin/<base>...HEAD
git diff --stat origin/<base>...HEAD
git log --oneline --decorate --no-merges origin/<base>..HEAD
Use these to answer:
- what files actually differ from the base right now
- which changes are functional versus cleanup/tooling/docs
- whether the existing PR title/body still matches the current branch after rebases, reverts, or scope narrowing
- Validate the current title and body.
python3 .codex/skills/gh-pr-metadata/scripts/validate_pr_metadata.py
- If the PR body needs a clean template scaffold, print one:
python3 .codex/skills/gh-pr-metadata/scripts/validate_pr_metadata.py --print-template
- Rewrite the PR title in conventional-commit style.
Rules:
- Prefer
type(scope): summary - Keep the title short and direct
- Use repo-typical types such as
fix,feat,docs,refactor,chore,test,ci,build,perf,revert - Keep the scope tight to the affected package or subsystem when useful
- Do not add prefixes like
[codex] - Make sure the title describes the current branch diff, not the original branch intent if the branch was later narrowed or partially reverted
- Rewrite the PR body to preserve the repo template structure:
## Description## Related Issue## Types of changes## Checklist
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 112 lines · 86 tokens per session scan A cd15d5df7194
gh-pr-metadata is a skill published in the GitHub repository module-federation/core (2,625 stars, last pushed 3d ago), licensed MIT. It adds 86 tokens to every session and 939 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-08-31.
Other skills, from other repositories
vercel-deploy
Deploy applications to Vercel with edge functions, serverless, and ISR.
v8-jit
V8 JIT optimization patterns for writing high-performance JavaScript in Next.js server internals. Use when writing or reviewing hot-path code in app-render, stream-utils, routing, caching, or any per-request code path. Covers hidden classes / shapes, monomorphic call sites, inline caches, megamorphic deopt, closure…
dce-edge
DCE-safe require() patterns and edge runtime constraints. Use when writing conditional require() calls, guarding Node-only imports (node:stream etc.), or editing define-env-plugin.ts / app-render / stream-utils for edge builds. Covers if/else branching for webpack DCE, TypeScript definite assignment, the NEXTRUNTIME…
migrate-radix-to-base
Migrates React projects and components from Radix UI to Base UI. Use when asked to migrate from radix, move to base-ui, convert radix primitives, or switch a shadcn project's base library. Handles single components ("migrate accordion") and whole projects.
copilotkit-develop
Use when building AI-powered features with CopilotKit v2 -- adding chat interfaces, registering frontend tools, sharing application context with agents, handling agent interrupts, and working with the CopilotKit runtime.
copilotkit-upgrade
Use when migrating a CopilotKit v1 application to v2 -- updating package imports, replacing deprecated hooks and components, switching from GraphQL runtime to AG-UI protocol runtime, and resolving breaking API changes.