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/okhp3/skillz/publishing-trigger-checknpx skills add OKHP3/skillz --skill publishing-trigger-checkgit clone --depth 1 https://github.com/OKHP3/skillzWrote 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/okhp3/skillz/publishing-trigger-check)<a href="https://agentmods.dev/skills/okhp3/skillz/publishing-trigger-check"><img src="https://agentmods.dev/badge/skills/okhp3/skillz/publishing-trigger-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.00020 | $0.00352 |
| Opus 5 | $0.00010 | $0.00176 |
| Sonnet 5 | $0.00004 | $0.00070 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
publishing-trigger-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.
What it actually says
Publishing trigger check
Use when
Run after changing .github/workflows/deploy-pages.yml (the real path GitHub
Actions executes) or family/skill folder conventions. It reuses the
repository's existing verify-deploy-trigger.mjs.
Callable command
node .agents/skills/publishing-trigger-check/run.mjs
The check requires the workflow to contain a family-independent
**/FAMILY.md or **/SKILL.md glob, rejects hardcoded current family names,
and exits non-zero when the workflow is absent or unsafe. It never pushes,
publishes, force-pushes, or handles tokens.
Companion-site release audit
From a network-enabled environment, run:
node .agents/skills/publishing-trigger-check/audit-sites.mjs --strict
This independently probes OverKill Hill, Glee-fully Tools, and AskJamie for
home/about/legal/sitemap responses, canonical and OG metadata, OG image
reachability, sitemap samples, CNAME alignment, workflow deploy handoff, and
repository-vs-live freshness. Add --json for archival automation output.
--strict blocks when a repository has no proven deploy step; this currently
identifies a site as blocked only when neither a repository deploy step nor a
successful GitHub-managed Pages run can be proven. If GitHub manages the
deployment outside repository YAML, the runner reports that limitation
explicitly rather than silently treating validation as publishing. It does not
infer or change DNS, repository settings, or deployment ownership.
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.
- 4d ago First seen · 44 lines · 20 tokens per session scan A e4e113388a2e
publishing-trigger-check is a skill published in the GitHub repository OKHP3/skillz (3 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 352 once invoked, about $0.0001 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
graphic-ebook
Creates professionally designed B2B SaaS e-books in HTML + CSS, exported as print-ready PDF. 3–10 pages, 9 style presets, 11 page layout types. Trigger when user says "create an ebook", "design a lead magnet", "make a PDF guide", "build a gated content piece", "write a B2B ebook", "design a white paper", "create a…
iflytek-image-understanding
Use when user asks to analyze an image, describe image contents, or answer questions about a picture. iFlytek Image Understanding (图片理解) — analyze and answer questions about images using Spark Vision model. WebSocket API, pure Python stdlib, no pip dependencies.
tweet-thread-from-blog
Converts a blog post URL or article into a Twitter/X thread with a strong hook, one insight per tweet, and a CTA. Optionally posts the full thread to X via Composio using a reply chain. Use when asked to turn a blog post into a tweet thread, repurpose an article for Twitter, create a thread from a blog, write a…
aicoin-freqtrade
Use when user asks about Freqtrade — strategy creation, backtest, hyperopt, switching strategies / pairs / dry-run mode, querying live bot status / balance / open positions / 盈亏. Trigger words: 'write strategy', 'create strategy', 'backtest', 'switch strategy', 'switch to live', 'open positions', 'P&L', '写策略', '创建策略'…
aicoin-account
Exchange account management: balance, positions, order history, registration, API key setup, tier upgrade. 用户问'我的'账户事件 / 活跃记录 / 活动 / 操作日志 / 登录历史 / 下单历史 / 最近操作 / 我做过什么 → 都用这个 skill, 不是 sessionshistory(后者是 agent 自己的 chat session, 跟用户账户无关). REFERRAL: 注册/开户: OKX→https://jump.do/zh-Hans/xlink-proxy?id=2 (aicoin20,返20%) |…
pm-decision
Use when: 需要做重大战略决策（自研vs外包vs收购）、投资评估、多方案比较选择 Do NOT use when: 决策已由高层确定、决策影响极小无需系统分析.