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 debugging-signals-pipelinegit 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/debugging-signals-pipeline)<a href="https://agentmods.dev/skills/posthog/posthog-foss/debugging-signals-pipeline"><img src="https://agentmods.dev/badge/skills/posthog/posthog-foss/debugging-signals-pipeline/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/debugging-signals-pipeline"><img src="https://agentmods.dev/badge/skills/posthog/posthog-foss/debugging-signals-pipeline.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.00089 | $0.02291 |
| Opus 5.5 | $0.00036 | $0.00916 |
| Sonnet 5.5 | $0.00018 | $0.00458 |
| Haiku 4.5 | $0.00009 | $0.00229 |
Grade B, and why
debugging-signals-pipeline scanned grade B with 2 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 1mo 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
curl -s 'http://localhost:8123/' --data-binary \ Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s 'http://localhost:8081/api/v1/namespaces/default/workflows?query=ORDER+BY+StartTime+DESC&maximumPageSize=15' \ Copies of this mod
1 near-identical copy found in the catalogue:
- debugging-signals-pipeline — 94% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debugging the signals pipeline
Pipeline flow
emit_signals_from_fixture
→ signal-emitter (Temporal workflow)
→ buffer-signals (batches signals, 5s flush timer)
→ safety_filter_activity
→ flush_signals_to_s3_activity
→ signal_with_start_grouping_v2_activity
→ team-signal-grouping-v2 (30s batch collect window)
→ read_signals_from_s3_activity
→ get_embedding_activity + generate_search_queries_activity
→ run_signal_semantic_search_activity
→ match_signal_to_report_activity
→ assign_and_emit_signal_activity
→ wait_for_signal_in_clickhouse_activity
→ (if new report) signal-report-summary
→ fetch_signals_for_report_activity
→ report_safety_judge_activity
→ select_repository_activity (spawns Docker sandbox)
Emitting test signals
# Emit a single signal from the Zendesk fixture at offset 26
DEBUG=1 python manage.py emit_signals_from_fixture --type zendesk --team-id 1 --offset 26 --limit 1
# Clean up all signal data before re-emitting (avoids stale matches)
DEBUG=1 python manage.py cleanup_signals --team-id 1 --yes
# Check pipeline status
python manage.py signal_pipeline_status --team-id 1 --wait --expected-signals 1 --poll-interval 10
Always clean up before re-emitting to avoid stale embeddings causing phantom report matches.
Monitoring Temporal workflows
The Temporal UI runs at http://localhost:8081. The REST API is useful for scripted inspection.
List recent workflows
curl -s 'http://localhost:8081/api/v1/namespaces/default/workflows?query=ORDER+BY+StartTime+DESC&maximumPageSize=15' \
| python3 -c "
import sys, json
for wf in json.load(sys.stdin).get('executions', []):
info = wf['execution']
status = wf['status'].replace('WORKFLOW_EXECUTION_STATUS_', '')
print(f'{wf[\"startTime\"][:19]} {status:20s} {wf[\"type\"][\"name\"]:35s} {info[\"workflowId\"][:90]}')
"
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.
- 1mo ago First seen · 231 lines · 89 tokens per session scan B 54bd3155a1fc
debugging-signals-pipeline is a skill published in the GitHub repository PostHog/posthog-foss (728 stars, last pushed yesterday), licensed MIT. It adds 89 tokens to every session and 2,291 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-12.
debugging-signals-pipeline compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| debugging-signals-pipelinePostHog/posthog-foss | Skill | 728 | yesterday | MIT | B | 89 | Claude Code, Codex |
| hermes-s6-container-supervisionNousResearch/hermes-agent | Skill | 261k | yesterday | MIT | A | 20 | Claude Code, Codex |
| smoke-testgarrytan/gbrain | Skill | 32k | yesterday | MIT | A | 79 | Claude Code |
| competition-container-runtimezhaoxuya520/reverse-skill | Skill | 44k | 1mo ago | MIT | A | 109 | Codex |
| aks-troubleshootingmicrosoft/skills | Skill | 3.2k | yesterday | MIT | A | 221 | Claude Code |
| aks-gpu-inferencemicrosoft/skills | Skill | 3.2k | yesterday | MIT | A | 114 | Claude Code |
| aks-network-capturemicrosoft/skills | Skill | 3.2k | yesterday | MIT | A | 75 | Claude Code |