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 gertsylvest/meta-team --skill dembrandtgit clone --depth 1 https://github.com/gertsylvest/meta-teamWrote 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/gertsylvest/meta-team/dembrandt)<a href="https://agentmods.dev/skills/gertsylvest/meta-team/dembrandt"><img src="https://agentmods.dev/badge/skills/gertsylvest/meta-team/dembrandt/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/gertsylvest/meta-team/dembrandt"><img src="https://agentmods.dev/badge/skills/gertsylvest/meta-team/dembrandt.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.00045 | $0.00589 |
| Opus 5 | $0.00023 | $0.00295 |
| Sonnet 5 | $0.00009 | $0.00118 |
| Haiku 4.5 | $0.00005 | $0.00059 |
Grade A, and why
dembrandt 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 11d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dembrandt
Extract a website's design tokens (colors, typography, spacing, shadows, borders, components) into W3C DTCG-format .tokens.json using the Dembrandt CLI.
Instructions
The target URL is in $ARGUMENTS. If no URL is provided, ask the user for one before proceeding.
1. Check installation
which dembrandt || echo "not installed"
If not installed, use npx dembrandt in place of dembrandt in all commands below (no install required).
2. Run extraction
Default command — outputs W3C DTCG tokens to output/<domain>/<timestamp>.tokens.json:
dembrandt <url> --dtcg --save-output
Adjust flags based on the site:
| Situation | Flag to add |
|---|---|
| JS-heavy SPA or slow site | --slow |
| Cloudflare / bot-detection issues | --browser=firefox (install first: npx playwright install firefox) |
| Need dark mode tokens | --dark-mode |
| Mobile viewport (390×844) | --mobile |
Example for a resilient extraction:
dembrandt stripe.com --dtcg --save-output --browser=firefox --slow
3. Move output to project documentation
Dembrandt writes to output/<domain>/ by default. After extraction, move the files to the project's canonical design token location.
Derive a kebab-case short name from the site's domain (e.g. stripe.com → stripe, fonts.google.com → google-fonts) and run:
SITE_SLUG="<web_site_shortname_kebab>"
DEST="project-docs/project-documentation/design-tokens/$SITE_SLUG"
mkdir -p "$DEST"
mv output/<domain>/* "$DEST/"
Confirm the files are in place:
ls "$DEST"
4. Report to the user
Report the final file paths and summarize what token categories were extracted (colors, typography, spacing, shadows, borders, components, etc.).
5. Next steps (optional)
If the task requires integrating extracted tokens into the project:
- Copy relevant tokens into the project's design token file (CSS variables, YAML, or the project's existing format)
- Update
design-vision.mdto note the reference site and any borrowed tokens
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.
- 11d ago First seen · 73 lines · 45 tokens per session scan A d7be69d5b8d5
dembrandt is a skill published in the GitHub repository gertsylvest/meta-team (5 stars, last pushed 1mo ago), licensed MIT. It adds 45 tokens to every session and 589 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-31.
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…
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…
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…