Borrowing it
Nothing to install: this file belongs to PostHog/posthog-foss. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/PostHog/posthog-foss/master/.agents/skills/managing-dashboards/SKILL.mdgit 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/managing-dashboards)<a href="https://agentmods.dev/skills/posthog/posthog-foss/managing-dashboards"><img src="https://agentmods.dev/badge/skills/posthog/posthog-foss/managing-dashboards/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/managing-dashboards"><img src="https://agentmods.dev/badge/skills/posthog/posthog-foss/managing-dashboards.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Prompt Injection · line 74 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 118 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
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.00109 | $0.01867 |
| Opus 5 | $0.00055 | $0.00933 |
| Sonnet 5 | $0.00022 | $0.00373 |
| Haiku 4.5 | $0.00011 | $0.00187 |
Grade A, and why
managing-dashboards 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Managing dashboards
Use this skill for a dashboard change that affects the dashboard platform, dashboard scene, or an existing non-widget tile type.
Use manage-dashboard-widgets for a new widget_type or a WidgetCard change.
1. Route the request
| Request | Primary path |
|---|---|
| Dashboard metadata, tile lifecycle, filters, variables, refresh, list, or layout | This skill |
| Public links, sharing settings, embeds, exports, or product-embedded dashboards | This skill |
| Dashboard template creation, editing, scope, or copying | This skill |
New or changed widget_type, widget config, widget query, or WidgetCard |
manage-dashboard-widgets |
Before coding, decide the effect on each surface. Record affected, unaffected, or not applicable.
- Authenticated dashboard
- Public shared dashboard
- Embedded dashboard
- Exported dashboard
- Product-embedded dashboard
- Dashboard template
- Dashboard list and project homepage, if the change changes metadata or visibility
Read surfaces and ownership before you select files.
2. Define feature intake and acceptance criteria
Do this before implementation for a new dashboard feature. Skip it for a narrow bug fix with an existing contract.
- State the user problem, intended actor, and explicit non-goals.
- State the feature action and its default behavior.
- State where the feature stores its state: dashboard, tile, request, user, URL, or a separate team-scoped resource.
- State the availability, read permission, and mutation permission.
- State behavior for new rows, existing rows, and invalid or absent state.
- State the acceptance criteria for allowed, denied, shared, and failure paths.
- State the expected query, cache, and database-write effect.
- State the metric or event that shows adoption, failure, or regression.
- If the feature adds persisted state or relations, define migration, cleanup, and concurrent-edit behavior.
- Check whether the user-facing API, setting, or workflow needs a documentation update.
What ships with it
8 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.
- references/access-sharing-and-embeds.md 3.4 KB
- references/backend-contracts-and-operations.md 6.6 KB
- references/data-models-and-collaboration.md 4.3 KB
- references/feature-lifecycle-and-rollout.md 4.3 KB
- references/filters-variables-and-overrides.md 2.6 KB
- references/layout-responsive-and-templates.md 2.9 KB
- references/querying-caching-and-scale.md 3.3 KB
- references/surfaces-and-ownership.md 3.1 KB
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.
- 5d ago Changed · +3 lines 0a3f931032a8
- 9d ago First seen · 138 lines · 109 tokens per session scan A aa7aa2050f2f
managing-dashboards is a skill published in the GitHub repository PostHog/posthog-foss (714 stars, last pushed today), licensed MIT. It adds 109 tokens to every session and 1,867 once invoked, about $0.0005 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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…