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 PolicyEngine/policyengine-claude --skill policyengine-standardsgit clone --depth 1 https://github.com/PolicyEngine/policyengine-claudeWrote 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/policyengine/policyengine-claude/policyengine-standards)<a href="https://agentmods.dev/skills/policyengine/policyengine-claude/policyengine-standards"><img src="https://agentmods.dev/badge/skills/policyengine/policyengine-claude/policyengine-standards/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/policyengine/policyengine-claude/policyengine-standards"><img src="https://agentmods.dev/badge/skills/policyengine/policyengine-claude/policyengine-standards.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00144 | $0.03060 |
| Opus 5.5 | $0.00058 | $0.01224 |
| Sonnet 5.5 | $0.00029 | $0.00612 |
| Haiku 4.5 | $0.00014 | $0.00306 |
Grade A, and why
policyengine-standards 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.
How it starts
The opening of the file, as written. The whole thing — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PolicyEngine development standards
Load this before committing to, reviewing, or setting up any PolicyEngine repository. It encodes the org conventions that CI enforces — the things a frontier model would otherwise guess wrong. For prose style (blog posts, PR bodies, docs) see the policyengine-writing skill.
Environment: uv + a local .venv
All PolicyEngine Python work uses uv with a .venv at the
repository root. Never use bare pip, and never run bare python/pytest.
uv venv # creates ./.venv (uv picks the interpreter from pyproject.toml)
uv pip install -e ".[dev]" # editable install with dev extras
uv run pytest # run anything through uv so it uses ./.venv
- Python version is per-repo — check
pyproject.toml(requires-python). The org spans the 3.13/3.14 era; there is no single global version. Do not downgrade a repo to satisfy a stale assumption, and do not hardcode a version across repos. uv run <cmd>guarantees the command runs in the repo's.venvwith its locked deps. Barepython script.py/pytestis the most common cause of "works locally, fails in CI".- Verifying "latest": if asked for the latest version of a package, read PyPI
(
https://pypi.org/pypi/<pkg>/json→info.version) immediately before pinning. Never infer "latest" from a lockfile, a local install, or search snippets.
Documentation builds
Python docs use Jupyter Book 2.0 (MyST-NB) — build with myst build docs, never jb build
(that is Jupyter Book 1.x). Use MyST markdown syntax.
Before committing — checklist
- Write the test first (TDD, below).
- Format:
make format(oruv run ruff format .for Python,bun run lint -- --fix && bunx prettier --write .for JS). - Run tests:
make test(oruv run pytest). - Add a changelog fragment (towncrier, below).
- Reference the issue in the PR: "Fixes #123".
Creating pull requests
The CI waiting problem
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 · 266 lines · 144 tokens per session scan A 3987eda2a6b0
policyengine-standards is a skill published in the GitHub repository PolicyEngine/policyengine-claude (32 stars, last pushed 2d ago), licensed MIT. It adds 144 tokens to every session and 3,060 once invoked, about $0.0006 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-08-30.
Other skills, from other repositories
adk-go-self-review
Review an ADK Go change the way a maintainer will — a fresh-context pass over the whole diff, five lenses (correctness and tests, scope, simplicity, style, adk-python parity), and the mutation check that proves your tests pin the change. Use before opening a PR, before any later push that changes code, and when asked…
adversarial-reviewer
Stress-test a code change for concrete correctness defects, unsafe assumptions, and failure modes. Use when the user explicitly asks for an adversarial review, a deep bug hunt, or to tear a change apart, or to check your own change before submitting it. Do not use for ordinary review, style feedback, or general…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
semgrep-rule-variant-creator
Creates language variants of existing Semgrep rules. Use when porting a Semgrep rule to specified target languages. Takes an existing rule and target languages as input, produces independent rule+test directories for each language.
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
include-test-files-that-assert-on-behavior-being-changed-in-decl
When delegating a task affected by this skill, include.