Borrowing it
Nothing to install: this file belongs to professorpalmer/Puppetmaster. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/professorpalmer/Puppetmaster/main/.cursor/skills/verify-puppetmaster-jev/SKILL.mdgit clone --depth 1 https://github.com/professorpalmer/PuppetmasterWrote 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/professorpalmer/puppetmaster/verify-puppetmaster-jev)<a href="https://agentmods.dev/skills/professorpalmer/puppetmaster/verify-puppetmaster-jev"><img src="https://agentmods.dev/badge/skills/professorpalmer/puppetmaster/verify-puppetmaster-jev/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/professorpalmer/puppetmaster/verify-puppetmaster-jev"><img src="https://agentmods.dev/badge/skills/professorpalmer/puppetmaster/verify-puppetmaster-jev.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.00041 | $0.00576 |
| Opus 5.5 | $0.00016 | $0.00230 |
| Sonnet 5.5 | $0.00008 | $0.00115 |
| Haiku 4.5 | $0.00004 | $0.00058 |
Grade A, and why
verify-puppetmaster-jev 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
Verify Puppetmaster Jev
Library plus CLI. Isolated temp store. Never use the user's live
.puppetmaster/ state. Never print an OpenRouter key.
Launch
Ready: python -m unittest tests.test_jev_transition -q exits 0 from
the Jev worktree (Puppetmaster-jev-oracle or the product checkout
that contains puppetmaster/jev/).
cd "$REPO"
.venv/bin/python -m unittest tests.test_jev_transition -q
Use the repo venv if present; otherwise python3 on PATH. Teardown is
the process exit. Helpers write under /tmp/verify-this/puppetmaster-jev/
and must not delete prior receipts.
Doctor
.cursor/skills/verify-puppetmaster-jev/scripts/doctor.py
Must report:
opted_in=falseandacting=falsein a cleared envtest_jev_transitionimportable- no
PUPPETMASTER_JEV/PUPPETMASTER_JEV_ACTleak from the host afterhermetic_envimport
If doctor fails, fix the tree. Do not drive live Decisions.
Drive
Prefer the helper, then unittest, then an optional live observe.
.cursor/skills/verify-puppetmaster-jev/scripts/prove_observe.py
Mapped features: features/README.md.
Evidence
A pass is:
- Helper JSON at
/tmp/verify-this/puppetmaster-jev/observe.json v1_acts_on_opt_in=true(auditor skipped withoutJEV_ACT)v234_match_today=true(launch / admit / enqueue unchanged)- Unittest exit 0
show/ stitcher preview contains## Jevonly when ajev_transitionGATE exists
Live Decisions are optional and only when the user named a key source. Load the key in-process. Never write it to evidence.
Cleanup
Kill only the helper/unittest PIDs this run started. Leave
/tmp/verify-this/puppetmaster-jev/ in place.
Helpers
.cursor/skills/verify-puppetmaster-jev/scripts/doctor.py.cursor/skills/verify-puppetmaster-jev/scripts/prove_observe.py
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 77 lines · 41 tokens per session scan A 38e1b080c612
verify-puppetmaster-jev is a skill published in the GitHub repository professorpalmer/Puppetmaster (471 stars, last pushed 3d ago), licensed MIT. It adds 41 tokens to every session and 576 once invoked, about $0.0002 per session on Opus 5.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-20.
Other skills, from other repositories
pn-testing-strategy
Testing strategy and pyramid. Unit/integration/E2E ratio, Vitest vs Playwright vs MSW, contract testing, and test-environment setup. Use when defining or reviewing a project's testing approach.
pn-test-generation
Generate unit or integration tests from code, specs, or acceptance criteria. Use when adding test coverage, scaffolding TDD, or backfilling tests for existing code.
web3-testing
Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols.
temporal-python-testing
Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.
data-quality-frameworks
Implement data quality validation with Great Expectations, dbt tests, and data contracts. Use when building data quality pipelines, implementing validation rules, or establishing data contracts.
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.