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/posthog/posthog-foss/hoglinpx skills add PostHog/posthog-foss --skill hogligit 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/hogli)<a href="https://agentmods.dev/skills/posthog/posthog-foss/hogli"><img src="https://agentmods.dev/badge/skills/posthog/posthog-foss/hogli.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.1 | $0.00047 | $0.00445 |
| Opus 5 | $0.00023 | $0.00222 |
| Sonnet 5 | $0.00009 | $0.00089 |
| Haiku 4.5 | $0.00005 | $0.00044 |
Grade A, and why
hogli 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 6d 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
hogli - PostHog Developer CLI
Unified CLI for PostHog development. Wraps all repo scripts, bin commands, and tooling behind a single entry point. There is no Makefile — hogli is the equivalent.
Run hogli --help to get the full, current command list. Run hogli <command> --help for any subcommand.
Process logging (for agents/debugging)
Where logs land depends on how the stack was launched:
Detached (hogli up -d) — phrocs writes files under .posthog/.generated/logs/ on every boot:
phrocs.log— the daemon's own stdio; the place to look when phrocs died at startup and the phrocs MCP tools are unreachable.<process>.log— per-process output (truncated on each start), where<process>matches the phrocs process key (seebin/mprocs.yaml).hogli doctor:reportprints thephrocs.logpath and tails its last lines.
TUI with hogli dev:setup --log, then hogli start — adds a tee wrap per process:
/tmp/posthog-<process>.log— full stdout+stderr; persists in the generated config untildev:setupis re-run without--log.
When the phrocs MCP is reachable, prefer mcp__phrocs__get_process_logs over grepping files.
Key references
hogli.yaml— command definitions (source of truth)tools/hogli-commands/hogli_commands/— PostHog-specific lazy Click command modulestools/hogli/README.md— framework documentationtools/hogli-commands/README.md— PostHog commands documentation
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.
- 6d ago First seen · 37 lines · 47 tokens per session scan A dcf22e56c617
hogli is a skill published in the GitHub repository PostHog/posthog-foss (714 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 445 once invoked, about $0.0002 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…