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 developing-subscriptionsgit 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/developing-subscriptions)<a href="https://agentmods.dev/skills/posthog/posthog-foss/developing-subscriptions"><img src="https://agentmods.dev/badge/skills/posthog/posthog-foss/developing-subscriptions/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/developing-subscriptions"><img src="https://agentmods.dev/badge/skills/posthog/posthog-foss/developing-subscriptions.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.00070 | $0.01702 |
| Opus 5.5 | $0.00028 | $0.00681 |
| Sonnet 5.5 | $0.00014 | $0.00340 |
| Haiku 4.5 | $0.00007 | $0.00170 |
Grade A, and why
developing-subscriptions 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 yesterday.
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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developing subscriptions
Use this skill for a change to the Subscriptions product or its delivery system.
Use the published managing-subscriptions skill to configure an existing subscription through MCP.
Use adding-product-alerting when delivery depends on a threshold, anomaly, breach, or recovery state.
When investigating a subscription whose insight is missing, or changing insight deletion or restoration, read the insight deletion and related-resource contract. It defines cleanup for subscriptions, alerts, and dashboard tiles, including single and bulk deletion and restore behavior.
1. Route the request
| Request | Primary path |
|---|---|
| Resource type, destination, schedule, delivery, lifecycle, or limits | This skill |
| Subscription API, permissions, MCP tools, or delivery history | This skill |
| Subscription creation or management UI | This skill |
| AI prompt report planning or output | This skill and integrating-with-posthog-ai |
| Threshold, anomaly, breach, recovery, or quiet hours | adding-product-alerting |
| Configure an existing subscription through MCP | Published managing-subscriptions |
Before implementation, name each affected boundary:
- Configuration and validation
- Persistence and schedule calculation
- Workflow queue and retry behavior
- Asset export or AI report generation
- Destination delivery
- Delivery history and failure notifications
- API, MCP, and frontend clients
- Billing, limits, and permissions
2. Define feature intake and acceptance criteria
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.
- yesterday Changed · +3 lines 6565eae0e3d1
- 5d ago Changed 0217369adb4d
- 8d ago Changed · +1 lines 0b3b82975fa3
- 1mo ago Changed · +3 lines 2d8cf083ccc6
- 1mo ago First seen · 135 lines · 70 tokens per session scan A 908353f4fae4
developing-subscriptions is a skill published in the GitHub repository PostHog/posthog-foss (726 stars, last pushed today), licensed MIT. It adds 70 tokens to every session and 1,702 once invoked, about $0.0003 per session on Opus 5.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-16.
Other skills, from other repositories
saga-orchestration
Implement saga patterns for distributed transactions and cross-aggregate workflows. Use this skill when implementing distributed transactions across microservices where 2PC is unavailable, designing compensating actions for failed order workflows that span inventory, payment, and shipping services, building…
platform-lightning-app-coordinate
Build complete Salesforce Lightning Experience applications from natural language descriptions. Use this skill when a user requests a "complete app", "Lightning app", "business solution", "management system", or describes a scenario requiring multiple interconnected Salesforce components (objects, fields, pages, tabs…
service-agentforce-channel-configure
Wires an existing, active Agentforce agent to a channel by resolving a fallback queue, setting up inbound routing (either PATCH SessionHandlerId on the MessagingChannel, or an inbound RoutingFlow for Voice/Email), and optionally configuring outbound escalation. Use when the user wants to add a channel to an existing…
commerce-app-migrate
Migrate an Adobe Commerce App Builder project from the Integration Starter Kit or Checkout Starter Kit to the new App Management approach. Run from the root of the App Builder project to be migrated. Pass --auto to skip confirmation prompts (suitable for CI or batch use) — auto mode prints a summary of all Q&A…
full-stack-orchestration-full-stack-feature
Coordinate database, backend, frontend, testing, and deployment work for a complete feature. Use when implementing changes that span multiple application layers.
multi-platform-apps-multi-platform
Build and deploy the same feature consistently across web, mobile, and desktop platforms using API-first architecture and parallel implementation strategies.