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 gemini-cli-extensions/sre --skill pre-publish-checkergit clone --depth 1 https://github.com/gemini-cli-extensions/sreWrote 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/gemini-cli-extensions/sre/pre-publish-checker)<a href="https://agentmods.dev/skills/gemini-cli-extensions/sre/pre-publish-checker"><img src="https://agentmods.dev/badge/skills/gemini-cli-extensions/sre/pre-publish-checker/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/skills/gemini-cli-extensions/sre/pre-publish-checker"><img src="https://agentmods.dev/badge/skills/gemini-cli-extensions/sre/pre-publish-checker.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.00038 | $0.00654 |
| Opus 5 | $0.00019 | $0.00327 |
| Sonnet 5 | $0.00008 | $0.00131 |
| Haiku 4.5 | $0.00004 | $0.00065 |
Grade C, and why
pre-publish-checker scanned grade C with 1 finding 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 10d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
1. **Do Not Simply Remove TODOs**: Do not delete `TODO` markers just to make the check pass. Instead: <!-- pre-publish-checker: ignore --> How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-Publish Checker
This skill guides you through a thorough audit of your project to ensure it meets publication standards. It combines automated script-based checks with a manual review workflow.
Policies
- Do Not Simply Remove TODOs: Do not delete
TODOmarkers just to make the check pass. Instead:- Action them: Resolve the task described.
- Move them: Transfer the
TODOto a tracking system (e.g., GitHub Issues) and replace the marker with a link to the issue.
- User Bypass: Any flagged issue can be bypassed if there is a valid reason. In
PUBLICATION_CHECKLIST.md, mark the status as[Pass]and include the keywordUSER_BYPASS: <explanation>.
Workflow
1. Initialization
- List all relevant files: Markdown (.md), code files (.py, .js, .go, etc.),
justfile, andREADMEs. - Create a
PUBLICATION_CHECKLIST.mdin the project root by copying the template fromreferences/checklist_template.md. - Populate the file list in the checklist.
2. Automated Audit
For each file in the checklist, run the automated check script:
uv run -s skills/pre-publish-checker/scripts/check_file.py <file_path>
Note: If uv is not available, use python3.
3. Iterative Review
- Process files one by one (or in small batches).
- Update the
PUBLICATION_CHECKLIST.mdwith the status and any issues found. - Fix issues as they are identified.
- For "long work", you can resume the process by reading the current state of
PUBLICATION_CHECKLIST.md. - Get a Synopsis: At any point, you can generate a quick summary of remaining work by running:
(Defaults to readinguv run -s skills/pre-publish-checker/scripts/summarize_checklist.pyPUBLICATION_CHECKLIST.md)
4. Final Verification
- Perform manual checks for "Google-bar professionalism" and overall quality.
- Ensure all boxes in
PUBLICATION_CHECKLIST.mdare checked.
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.
- 10d ago First seen · 57 lines · 38 tokens per session scan C c7b626ef4a4c
pre-publish-checker is a skill published in the GitHub repository gemini-cli-extensions/sre (83 stars, last pushed 7d ago), licensed Apache-2.0. It adds 38 tokens to every session and 654 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…