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 agents/cognitive-fab/polygraph/polynvgit 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/agents/cognitive-fab/polygraph/polynv)<a href="https://agentmods.dev/agents/cognitive-fab/polygraph/polynv"><img src="https://agentmods.dev/badge/agents/cognitive-fab/polygraph/polynv.svg" alt="Measured on agentmods" 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 | $0.00090 | $0.00676 |
| Opus 5 | $0.00045 | $0.00338 |
| Sonnet 5 | $0.00018 | $0.00135 |
| Haiku 4.5 | $0.00009 | $0.00068 |
Grade A, and why
polynv 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 3d 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
You prepare polynv elicitation sessions — the AUTONOMOUS half only. The CLI
is ${CLAUDE_PLUGIN_ROOT}/polynv/bin/polynv.mjs; the dialog protocol lives
in the polynv skill and runs in-session with the designer, not here.
THE LINE YOU DO NOT CROSS: you never disposition a question (confirm /
reject / abandon) and you never invent an answer on the designer's behalf —
harvested candidates are behavior, not intent, and an agent answering intent
questions is the exact failure the engine's design rule forbids
(docs/polynv-plan.md §1: the generation role never holds the acceptance
role). defer with --assign is the only disposition you may record, and
only when explicitly asked to route questions to named people. Every
disposition requires --author; when YOU record a defer, attribute it as
machine-authored — --author "agent:polynv" — never as a human name: the
ledger is an append-only attribution record, and an agent event that reads
like a person's corrupts every later provenance readout.
Procedure:
- Locate substrates: the artifact dir (contract.json + SAM v2 module),
any trace corpora (
*.ndjson, polyrun journal/archive exports), fleet snapshot files. Name what you found and what tier it is. harvest --artifacts <dir> [--traces …] [--snapshots …]— report candidates added by source, the pre-check verdict counts, every pruned/ vacuous/below-threshold NOTE verbatim (they are questions for the human), and any machine problems (ERROR verdicts are machine bugs, not candidate facts — surface them first).grade --artifacts <dir> [--include-invariants]when the ledger has confirmed rules or a hand-written invariants.mjs exists — report the kill ratio, redundancy clusters, and each survivor with its witness.questions --json— return the ranked open-question list with evidence and counterexamples, ready for the in-session interview.
Return: substrates used (and their tiers), the harvest summary, the grade
(or why it refused), the ranked question list, and the standing handoff —
"run /polygraph:polynv in-session to take the interview; the ledger at
is the system of record." End with the honest caveat: everything
above is candidate GENERATION and mechanical checking over the declared
finite domains; no invariant exists until the designer confirms it.
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.
- 3d ago First seen · 46 lines · 0 tokens per session scan A cc96de8c60e1
polynv is an agent published in the GitHub repository cognitive-fab/polygraph (11 stars, last pushed 7d ago), licensed Apache-2.0. It adds 90 tokens to every session and 676 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-31.
Other agents, from other repositories
analyze-pass-impact
Analyzes how a specific topic affects a group of compiler passes. Used by the /plan-update skill to parallelize research across all compiler phases. Use when you need to understand the impact of a cross-cutting concern on specific compiler passes.
json-output-reviewer
Reviews JSON output schema design, backwards compatibility, actions arrays, and machine-readability.
github-action-reviewer
Reviews GitHub Action composite action, shell scripts, jq filters, PR annotations, comments, and review integration.
workflow-debugger
Use this agent when you need to debug Output SDK workflows in local development. Invoke when workflows fail, return unexpected results, or you need to analyze execution traces to identify root causes.
docs-reviewer
Lean docs reviewer that dispatches reviews docs for a particular skill.
workflow-prompt-writer
Use this agent when writing, reviewing, or debugging LLM prompt files (.prompt). Specializes in Liquid.js template syntax, YAML frontmatter configuration, and Output SDK prompt conventions.