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/tomthebearded/guide-forge/pre-pr-checknpx skills add tomthebearded/guide-forge --skill pre-pr-checkgit clone --depth 1 https://github.com/tomthebearded/guide-forgeWrote 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/tomthebearded/guide-forge/pre-pr-check)<a href="https://agentmods.dev/skills/tomthebearded/guide-forge/pre-pr-check"><img src="https://agentmods.dev/badge/skills/tomthebearded/guide-forge/pre-pr-check.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.00136 | $0.02282 |
| Opus 5 | $0.00068 | $0.01141 |
| Sonnet 5 | $0.00027 | $0.00456 |
| Haiku 4.5 | $0.00014 | $0.00228 |
Grade A, and why
pre-pr-check 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 4d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: pre-pr-check
You are a release gatekeeper for the GuideForge repo. Before a contribution goes out as a PR, confirm the change respects every rule in CONTRIBUTING.md and leaves the repo internally consistent. Read-only: report, don't fix. If a check fails, say exactly which file/line and what the fix is, then let the contributor fix it and re-run.
Base to diff against: $ARGUMENTS (default develop, the branch every contribution targets — main holds
released state only).
Step 0 — Scope the change
Determine what this PR touches. Run:
git diff --name-status <base>...HEAD— files added / modified / renamed / deleted.git diff <base>...HEAD -- CHANGELOG.md— did the changelog move?
Group the changed files by area: skills/ (each skill's SKILL.md wrapper and its co-located
prompt.md contract), templates/, reference/, root docs (README.md, EXPLAINER.md,
CHANGELOG.md), .claude-plugin/, scripts/. The checks below key off which areas changed — skip a check
only when nothing in its area changed, and say so.
Step 1 — Run the automated gate (do this FIRST, don't eyeball it)
The deterministic checks are scripts, not prose you re-perform by hand. Run them and paste their real output into your report; a non-zero exit is a blocker, full stop.
node scripts/check-version.mjs— version stamps agree acrossplugin.json, the README badge, and the top releasedCHANGELOG.mdheader. Tagging is not checked (see below); confirm it by eye on a release PR.node scripts/check-consistency.mjs— skill frontmatternamematches folder; every skill with aprompt.mdinlines it via the cat-injection line; the stated skill count inREADME.md/marketplace.jsonmatches the actual folder count; every rule id cited resolves and every full-contract mirror (the four pipeline prompts +EXPLAINER.md) mentions every rule; no dead relative.mdlinks and no dead#anchorsin the docs/skills/templates.node scripts/doctor.mjs— advisory: whether your installed plugin cache is stale vs the working tree. Not a blocker, but if it reports STALE, remind the contributor their/plugininstall won't reflect these changes until they reinstall — so any "I tested it" claim may be against old code.
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.
- 4d ago First seen · 116 lines · 136 tokens per session scan A 39dfea8cb9a5
pre-pr-check is a skill published in the GitHub repository tomthebearded/guide-forge (3 stars, last pushed 14d ago), licensed MIT. It adds 136 tokens to every session and 2,282 once invoked, about $0.0007 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
feedback
Guide the user to open a feedback issue for the simple-output-styles plugin. Use when the user wants to report feedback on an output style, the evals, the documentation, the installation, licensing, or wants to request a new style. Gathers the Claude Code version and the active style, then prepares a prefilled GitHub…
pick
Help the user pick an output style from the simple-output-styles plugin and set it globally. Recommends actionable-clarity, or walks through the full list with the pros and cons of each style.
diataxis
Classify, create, review, and maintain documentation using the Diátaxis framework — the four-quadrant system (tutorials, how-to guides, reference, explanation) that separates documentation by user need. Use this skill whenever the user wants to classify documentation into quadrants, perform a documentation gap…
changelog
Generate, update, review, and maintain changelogs using Keep a Changelog format, semantic-release, and conventional commits. Use this skill whenever the user wants to add a changelog entry, prepare release notes, document version changes, generate a changelog from git history, configure semantic-release, understand…
api-documentation
Patterns and templates for creating comprehensive API documentation using OpenAPI/Swagger, AsyncAPI, and manual documentation approaches. Use this skill whenever the user wants to document REST endpoints, generate or improve an OpenAPI spec, create Swagger docs, document WebSocket/event-driven APIs with AsyncAPI…
documentation-standards
Standards and patterns for creating, reviewing, and improving technical documentation — covering markdown formatting, heading hierarchy, code blocks, links, writing style, accessibility, and language-native doc toolchains (rustdoc, godoc, Sphinx, TypeDoc, Javadoc, DocC, ExDoc). Use this skill whenever the user wants…