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.
git clone --depth 1 https://github.com/cognitive-fab/polygraphWrote 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/plugins/cognitive-fab/polygraph/polyviz)<a href="https://agentmods.dev/plugins/cognitive-fab/polygraph/polyviz"><img src="https://agentmods.dev/badge/plugins/cognitive-fab/polygraph/polyviz/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/plugins/cognitive-fab/polygraph/polyviz"><img src="https://agentmods.dev/badge/plugins/cognitive-fab/polygraph/polyviz.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
polyviz 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 1mo 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
{
"name": "polyviz",
"displayName": "polyviz",
"version": "0.1.0",
"description": "A deterministic, artifact-derived diagram renderer for Polygraph. Turns the artifacts the suite already produces — the state machine, the invariants, the counterexample, the polyvers compat verdict — into a fixed catalog of clean, brand-consistent SVGs (optional PNG). Same inputs → byte-identical output; no model call at render time. Renders from a viz-model JSON or straight from a Polygraph/polyvers artifacts directory (adapters derive the machine graph by bounded BFS over the module, read the invariants, resolve a failing findings.json to its counterexample trace, and map compat-report.json). Optional runtime components: the state-machine graph needs elkjs and PNG needs @resvg/resvg-js (both optionalDependencies, loaded lazily); the pure viz-model → SVG path needs neither and executes no user code. Deriving the machine graph from a real run does execute the target module (bounded reachability).",
"author": {
"name": "jdubray",
"url": "https://github.com/jdubray"
},
"homepage": "https://github.com/cognitive-fab/polygraph",
"repository": "https://github.com/cognitive-fab/polygraph",
"license": "Apache-2.0",
"keywords": [
"visualization",
"diagram",
"svg",
"state-machine",
"verification",
"polygraph",
"polyvers",
"deterministic",
"counterexample"
]
}
What it installs
The manifest is a name and a version. 1 skill, 1 command, 1 agent travel with it, and installing the plugin installs all of them — 173 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 1mo ago First seen · 25 lines scan A 62dd7fa32e0f
polyviz is a plugin published in the GitHub repository cognitive-fab/polygraph (14 stars, last pushed 1mo ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
quarto
Collection of skills for Quarto document creation.
animal-geneticist-breeder
Reasons from additive genetic variance, response to selection (R = i h sigmaA), accuracy, and inbreeding depression through REML/BLUP and ssGBLUP pipelines (BLUPF90, ASReml, WOMBAT), economic selection indices, optimum-contribution mate allocation, and Interbull MACE while treating confounded contemporary groups, pred.
catalysis-scientist
Reasons from active-site structure, turnover frequency, selectivity, and the Sabatier principle through CO/H2 chemisorption site-counting, Weisz-Prater and Mears transport checks, Langmuir-Hinshelwood/Mars-van Krevelen kinetics, and operando DRIFTS/XAS while treating diffusion-limited apparent rates, DRIFTS spectator…
agricultural-engineer
Reasons from mass, energy, and momentum balances on variable biological media through ET-based scheduling, psychrometric grain-drying balances, ASABE D497 draft estimates, EPANET pipe networks, and RTK-GNSS/ISOBUS precision-ag validation while treating soil compaction, clogged drip emitters, grain-bin hotspots, GPS…
algebraist
Reasons from carriers, operations, and morphisms through isomorphism theorems, universal properties, exact-sequence and homological tools (Ext, Tor, snake lemma), and computational systems like GAP, Magma, SageMath, and Lean while treating silently smuggled hypotheses (commutativity, units, Noetherian, algebraically…
antimicrobial-resistance-scientist
Reasons from MIC distributions, ECOFFs, and phenotype–genotype concordance through EUCAST/CLSI AST, CARD/RGI and AMRFinderPlus resistomes, GLASS/WHONET/NARMS surveillance, carbapenemase/ESBL/MRSA mechanism panels, and heteroresistance PAP while treating breakpoint mixing, genotype-without-phenotype overclaim…