quill-code

quill-code is a skill for Claude Code from PostHog/posthog-foss. It costs 84 tokens per session (1,362 once invoked), scanned A, original, MIT.

A guide for changing the Quill design system, a shared collection of interface components and visual design rules, and testing those changes in the desktop app.

In plain words
What is it for?
Use it to edit Quill components, build a local package, install it in the desktop product, and verify the result.
Why use it?
It explains how to test unpublished design-system changes locally without publishing them first.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to edit Quill components, build a local package, install it in the desktop product, and verify the result.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/posthog/posthog-foss/quill-code
Install

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.

Any agent
npx skills add PostHog/posthog-foss --skill quill-code
Clone the repo
git clone --depth 1 https://github.com/PostHog/posthog-foss

Made for: Claude Code.

Wrote 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.

agentmods badge for quill-code

README.md
[![agentmods](https://agentmods.dev/badge/skills/posthog/posthog-foss/quill-code/github.svg)](https://agentmods.dev/skills/posthog/posthog-foss/quill-code)
Your own site
<a href="https://agentmods.dev/skills/posthog/posthog-foss/quill-code"><img src="https://agentmods.dev/badge/skills/posthog/posthog-foss/quill-code/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.

agentmods 80×15 button for quill-code

Your own site · 80×15
<a href="https://agentmods.dev/skills/posthog/posthog-foss/quill-code"><img src="https://agentmods.dev/badge/skills/posthog/posthog-foss/quill-code.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 84 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,362 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to high

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 →

  • high Tool Misuse · line 53
    Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
    Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00084 $0.01362
Opus 5 $0.00042 $0.00681
Sonnet 5 $0.00017 $0.00272
Haiku 4.5 $0.00008 $0.00136

Measured 7d ago against content hash f0df72ad7f50, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

quill-code 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 7d 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.

products/desktop/.claude/skills/quill-code/SKILL.md · 108 lines

How it starts

The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.

quill-code

@posthog/quill's source lives in this monorepo at packages/quill (repo root, two levels up from products/desktop). Desktop still consumes the published npm package via its nested workspace catalog — products/desktop is excluded from the root pnpm workspace, so workspace: linking cannot reach it. To test an unpublished quill change here, you build quill in-repo, pack it to a tarball, and point a pnpm overrides entry at that tarball. This is a temporary local-dev state — revert before merging (see below).

All commands below run from products/desktop/. Building quill uses the root workspace's install, so run pnpm install at the monorepo root once first.

Quill layout (where to edit)

packages/quill (from the monorepo root) is the workspace (@posthog/quill-workspace). It contains sub-packages, each a layer of the design system:

  • packages/primitives/src — base components (Card, Badge, Button, Progress, …)
  • packages/components/src — composed components (DataTable, DateTimePicker, Metric)
  • packages/blocks/srcproduct-level blocks (e.g. ExperimentCard). Add the file here and export it from packages/blocks/src/index.ts.
  • packages/quill/src — the aggregate that re-exports all layers as @posthog/quill.

A new export in any sub-package flows to @posthog/quill automatically on build.

The loop (every quill change)

  1. Edit/add the component in the right sub-package (above) and export it from that package's src/index.ts.

  2. Re-sync into products/desktop manually — build → pack → point the override → reinstall:

    # From products/desktop/
    DESKTOP_ROOT="$PWD"
    QUILL_DIR="${QUILL_DIR:-../../packages/quill/packages/quill}"
    
    # a. Build the WHOLE quill workspace (two levels up from the aggregate), so the
    #    sub-packages rebuild BEFORE the aggregate bundles them.
    ( cd "$QUILL_DIR/../.." && pnpm build )
    
    # b. Pack into .local-quill/ under a UNIQUE filename. pnpm pins a tarball by
    #    integrity, so a stable name caches stale across re-syncs — drop old local
    #    tarballs first, then rename the packed file to a unique local name.
    #    (Anchor on $DESKTOP_ROOT, not `git rev-parse --show-toplevel`: the git
    #    toplevel is the monorepo root, not this workspace.)
    rm -f .local-quill/posthog-quill-local-*.tgz
    ( cd "$QUILL_DIR" && npm pack --pack-destination "$DESKTOP_ROOT/.local-quill" )
    mv .local-quill/posthog-quill-[0-9]*.tgz ".local-quill/posthog-quill-local-$(git rev-parse --short HEAD)-$$.tgz"
    
    # c. Point the override at the new tarball, then reinstall.
    #    Edit pnpm-workspace.yaml so overrides['@posthog/quill'] = file:./.local-quill/<new file>
    pnpm install
    

Read the full file on GitHub · 108 lines

Changes

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.

  1. 7d ago First seen · 108 lines · 84 tokens per session scan A f0df72ad7f50

Subscribe to this mod's changes

quill-code is a skill published in the GitHub repository PostHog/posthog-foss (715 stars, last pushed today), licensed MIT. It adds 84 tokens to every session and 1,362 once invoked, about $0.0004 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.

Related

Other skills, from other repositories

chakra-ui-builder

Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…

chakra-ui/chakra-ui · 214 tokens

visual-ralph

Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.

Yeachan-Heo/oh-my-codex · 50 tokens

frontend-visual-qa

Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…

daymade/claude-code-skills · 145 tokens

prototype-web

A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.

nexu-io/html-anything · 24 tokens

animation-principles

Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.

Owl-Listener/designer-skills · 59 tokens

refactoring-ui

Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent…

wondelai/skills · 132 tokens