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 PostHog/posthog-foss --skill checking-deploy-timinggit clone --depth 1 https://github.com/PostHog/posthog-fossWrote 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/posthog/posthog-foss/checking-deploy-timing)<a href="https://agentmods.dev/skills/posthog/posthog-foss/checking-deploy-timing"><img src="https://agentmods.dev/badge/skills/posthog/posthog-foss/checking-deploy-timing/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/posthog/posthog-foss/checking-deploy-timing"><img src="https://agentmods.dev/badge/skills/posthog/posthog-foss/checking-deploy-timing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00128 | $0.00895 |
| Opus 5 | $0.00064 | $0.00447 |
| Sonnet 5 | $0.00026 | $0.00179 |
| Haiku 4.5 | $0.00013 | $0.00089 |
Grade A, and why
checking-deploy-timing 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 9d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- checking-deploy-timing — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Checking when something was deployed
PostHog's CI writes a deploy marker into the project as an annotation every time a commit
ships to an environment. These annotations are hidden_in_user_interface: true, so they don't
show in the UI and are easy to forget — but they are the source of truth for "when did this go
out". Always check them when staff ask about deploy timing, rather than inferring from when a
metric or event volume changed (that conflates a capture change with a query/code change).
The deploy annotations
List them with posthog:annotations-list using {"search": "deploy"}. Each deploy marker looks like:
content:Deployed PostHog/posthog@<sha> to <env>— env isprod-us,prod-eu, ordevcreation_type:GITscope:organizationhidden_in_user_interface:truedate_marker: the deploy time (UTC)
They're returned newest-first; paginate with offset if you need to go further back.
Workflow
-
Find the change's merge commit. Identify the PR (e.g.
gh search prs --repo PostHog/posthog --author <user> "<keywords>"), thengh pr view <n> --repo PostHog/posthog --json number,title,mergedAt,mergeCommit,state. Note the merge commit SHA andmergedAt. -
List the target environment's deploys around the merge, oldest-first. Match the region the user asked about (
prod-usfor "the US",prod-eufor "the EU"). The annotations come back newest-first, so don't just take the first... to <env>match on page 1 — that's the most recent deploy. Paginate (withoffset) until you reach markers aroundmergedAt, then consider that environment's deploys in chronological order, starting with the first whosedate_markeris aftermergedAt. Check them earliest-first in step 3. -
Confirm the deployed commit actually contains the merge commit. A later
date_markeris necessary but not sufficient — a deploy can fire just after the merge yet build a slightly older commit. Verify ancestry:gh api repos/PostHog/posthog/compare/<merge_sha>...<deployed_sha> --jq '{status,ahead_by,behind_by}'
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.
- 9d ago First seen · 44 lines · 128 tokens per session scan A 54b21ebec868
checking-deploy-timing is a skill published in the GitHub repository PostHog/posthog-foss (715 stars, last pushed today), licensed MIT. It adds 128 tokens to every session and 895 once invoked, about $0.0006 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-09-03.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".