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/cognitive-fab/polygraph/polygennpx skills add cognitive-fab/polygraph --skill polygengit clone --depth 1 https://github.com/cognitive-fab/polygraphWhat 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 | $0.00201 | $0.03218 |
| Opus 5 | $0.00101 | $0.01609 |
| Sonnet 5 | $0.00040 | $0.00644 |
| Haiku 4.5 | $0.00020 | $0.00322 |
Grade A, and why
polygen 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 2d 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
polygen — author verifiable code, out of the box
Companion to the polygraph skill. That one AUDITS code that already exists.
This one AUTHORS new code so it's verifiable from the start — closing the loop
at creation time instead of retrofitting it later. v1 is JS/TS only: the
generated module is directly usable only in a JS/TS codebase (porting a
verified model to another language is a real, separate problem — the port
itself would need its own differential check against the JS original — and is
out of scope here).
The authored artifact (v0.7): by default a SAM v2 strict-profile
module (module.exports = { instance, init, actions, getState, setState },
sam-lib 2.1.2 vendored in the plugin): named intents with schemas and
finite domains, acceptors keyed by intent name, every not-applicable action
an observable reject(reason) (never a throw), sealed model, and explicit
next-state (prime) semantics — acceptors write the next draft and frame
untouched variables with unchanged(...) (sam-lib 2.1, #25). Generated code
must load strict-clean — instance({}).validate() is a hard gate at
every stage boundary, so schema/shape errors block instead of becoming report
lines, and dead wiring cannot ship silently. The self-repair loop feeds back
lastStep() classifications and determinism flags, not only windows and
invariants. (House rule from sam-lib #29, fixed in 2.0.0-alpha.2: never rely on
instance({}).state(); the pipeline uses getState()/setState() only.)
Same disclosure as
polygraph. This is experimental, unproven technology and a consistency check, not a proof. A converged run means the authored code satisfies its OWN stated invariants over a bounded, explored state space — nothing more, and that space is finite only because the contract declares finite action/data domains; behavior at values outside the declared representatives is unchecked. The contract and the invariants are the model's reading of your intent; they need your review before either is trusted.
All scripts live under ${CLAUDE_PLUGIN_ROOT}/scripts/. polygen.mjs needs
ANTHROPIC_API_KEY and an explicit --model (no default; recommend opus-5
with the self-repair loop on, which is the default — fable-5 only for
one-shot runs with --repair-max 0, and opus-4.8 as the retry if the API
refuses on policy grounds. Per-step source of truth: RECOMMENDED_MODELS in
scripts/models.mjs).
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.
- 2d ago First seen · 222 lines · 0 tokens per session scan A b4e5306a2327
polygen is a skill published in the GitHub repository cognitive-fab/polygraph (11 stars, last pushed 5d ago), licensed Apache-2.0. It adds 201 tokens to every session and 3,218 once invoked, about $0.0010 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
electron-node-upgrade
Guide for performing Node.js version upgrades in the Electron project. Use when working on the roller/node/main branch to fix patch conflicts during e sync --3. Covers the patch application workflow, conflict resolution, analyzing upstream Node.js changes, building, running the Node.js test suite, and proper commit…
lint-js
Lint JS/TS code only. Use before opening a PR when only JavaScript or TypeScript files were changed (no Rust).
Shade dropdown surface contract
DropdownMenu, Select, and Popover share one visual recipe (bg-surface-elevated-2 + border-border/60 dark:border-border/30 + shadow-md). Change them together. Trigger when editing any of those three Shade files.
Shade ShadCN install
Guardrails for running pnpm dlx shadcn@latest add in Shade — never overwrite existing components, fresh branch first, swap raw colours for semantic tokens after integrating. Trigger when the user proposes a shadcn add, or when a fresh ShadCN-shaped file lands in apps/shade/src/components/ui.
Shade use primitives
Replace bare divs that only carry flex/grid/gap utilities with Shade primitives (Stack, Inline, Box, Grid, Container, Text). Use semantic gap="md" instead of gap-4. Trigger when editing TSX in Shade-consuming apps.
geometry-and-math
Use this skill when using Phaser 4 math and geometry utilities. Covers vectors, rectangles, circles, triangles, polygons, random number generation, angles, distance, interpolation, and snapping. Triggers on: Vector2, Rectangle, Circle, math, distance, angle, random, lerp.