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 ralfyishere/rules-with-receipts --skill publish-hygienegit clone --depth 1 https://github.com/ralfyishere/rules-with-receiptsWrote 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/ralfyishere/rules-with-receipts/publish-hygiene)<a href="https://agentmods.dev/skills/ralfyishere/rules-with-receipts/publish-hygiene"><img src="https://agentmods.dev/badge/skills/ralfyishere/rules-with-receipts/publish-hygiene/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/ralfyishere/rules-with-receipts/publish-hygiene"><img src="https://agentmods.dev/badge/skills/ralfyishere/rules-with-receipts/publish-hygiene.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.00129 | $0.01391 |
| Opus 5 | $0.00064 | $0.00696 |
| Sonnet 5 | $0.00026 | $0.00278 |
| Haiku 4.5 | $0.00013 | $0.00139 |
Grade A, and why
Publish Hygiene scanned grade A 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 11d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Rules files, prompts, and agent configs are code that executes in whatever session loads them. Before loading one: read it end to end; refuse or flag network fetches, curl-pipe-bash, credential access, out-of-project wri How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Publish Hygiene
Purpose
Publishing is an R3 change with a twist: the blast radius is permanent (caches, mirrors, forks) and the failure modes live in layers that normal review never looks at. Content gets scrubbed; the git history, commit metadata, and licensing don't. This skill is the checkable procedure for crossing the public boundary in either direction: pushing things out, or pulling untrusted instruction files in.
When to use this skill
- Before any visibility flip, repo transfer, package publish, or external post of previously-private material.
- Before committing third-party files into any repo (rights check), or loading third-party rules/instruction files into tool-empowered sessions (injection check).
- When sanitizing a private artifact for public release.
When NOT to use this skill
- Content that was authored public-first with no private lineage and no third-party material — the standard
change-controlR3 confirmation suffices. - Don't re-run the full procedure on every push to an already-public repo; the boundary crossing is the event, not each commit after it (the recurring scan lives in the maintenance cadence).
Operating procedure
Publishing outward — four layers, checked in order:
- Content layer. Grep every file for secrets (key patterns, tokens, private-key headers), personal identifiers (usernames, hostnames, emails not meant as public identity), business specifics, and machine paths. Scrub, then re-grep to prove it: the audit must come back empty, not "looked fine."
- Metadata layer. Git history stores authors and committers separately — a single bare
git commitleaks[email protected]even when content is clean. Checkgit log --format='%ae %ce' | sort -uacross ALL history. Also: file timestamps, EXIF in images, embedded absolute paths in generated files. - History layer. A sanitized tree on top of an unsanitized history publishes the history. If the project has private lineage, publish a fresh history (orphan branch or new repo, one clean initial commit). Never assume old commits are invisible because the current tree is clean.
- Rights layer. Every third-party file needs redistribution rights you can name. Default when unsure: cite (source repo + commit SHA), don't copy.
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.
- 11d ago First seen · 66 lines · 0 tokens per session scan A 2daea18976b6
Publish Hygiene is a skill published in the GitHub repository ralfyishere/rules-with-receipts (2 stars, last pushed 2mo ago), licensed MIT. It adds 129 tokens to every session and 1,391 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
alterlab-fda
Query the openFDA API for drugs, medical devices, adverse event reports, recalls, regulatory submissions (510k, PMA), and substance identification (UNII). Use when searching FDA safety data, pharmacovigilance and adverse-event signals, device clearances, drug labels, or recall records for regulatory data analysis and…
alterlab-uspto
Access USPTO APIs for patent and trademark searches, examination history (PEDS), assignments, citations, office actions, and trademark status (TSDR). Use when searching patents or trademarks, conducting prior art searches, retrieving patent examination or assignment records, or doing intellectual property (IP)…
alterlab-iso13485
Prepares ISO 13485 certification documentation for medical device Quality Management Systems (QMS) — gap analysis of existing documentation, Quality Manuals, required procedures and work instructions, and Medical Device Files. Use for ISO 13485 QMS documentation, conducting a documentation gap analysis, drafting a…
cold-email
B2B-Outreach-E-Mails im deutschen und DACH-Kontext konservativ entwerfen und prüfen. Nutze diesen Skill für Kaltakquise-Mails, Nachfassnachrichten, Betreffzeilen und Outreach-Sequenzen an Geschäftskontakte, und für die vorgelagerte Frage, ob eine geplante Ansprache überhaupt zulässig ist. Prüft § 7 UWG, die…
bodily-injury-claims-processing
Review and structure auto insurance bodily injury claims, including intake triage, evidence completeness, injury causation, treatment chronology, medical necessity, wage-loss support, negotiation risks, and human escalation. Use when analyzing bodily injury claim files, designing claims-agent workflows, drafting…
cite-specific-section-numbers
Anchor document analysis to exact sections or pages so readers can verify the supporting passage.