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/policyengine/policyengine-claude/policyengine-plugin-maintenancenpx skills add PolicyEngine/policyengine-claude --skill policyengine-plugin-maintenancegit 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-plugin-maintenance)<a href="https://agentmods.dev/skills/policyengine/policyengine-claude/policyengine-plugin-maintenance"><img src="https://agentmods.dev/badge/skills/policyengine/policyengine-claude/policyengine-plugin-maintenance.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.00126 | $0.01776 |
| Opus 5 | $0.00063 | $0.00888 |
| Sonnet 5 | $0.00025 | $0.00355 |
| Haiku 4.5 | $0.00013 | $0.00178 |
Grade C, and why
policyengine-plugin-maintenance scanned grade C with 1 finding 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 4d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf ~/.claude/plugins/cache/policyengine-claude How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maintaining the PolicyEngine skills catalog
This skill is for maintaining the skills SOURCE repo and the Claude wrapper — not for using PolicyEngine.
Repository shape (rebuilt)
Flat, category-tagged skills compiled into install profiles, then rendered into per-target wrappers.
skills/<name>/SKILL.md— one flat directory per skill (nodomain-knowledge/,tools-and-apis/nesting). Frontmatter isname(equal to the dir name), adescription:block that carries trigger phrases and stays under 1024 characters (hard Codex limit), andmetadata.category. Supporting files sit beside SKILL.md — e.g.skills/policyengine-content/templates/social-image.html.bundles/*.json— install profiles. Each lists the skills, commands, and agents it ships by path.complete.jsonis the recommended everything bundle; the rest are scoped (essential, country-models, analysis-tools, app-development, api-development, data-science, dashboard-builder, content).targets/claude/— the Claude wrapper source:marketplace.template.json,agents/,commands/,hooks/hooks.json,lessons/.targets/codex/is the Codex target.scripts/build_claude_wrapper.py— compiles the bundles and marketplace template into the generatedpolicyengine-claudemarketplace, validating that every referenced skill, command, and agent path exists (and normalizing plugin entries for the current Claude Code schema).presets/,analyses/,dashboard/,mcp/— analysis infrastructure consumed by the commands and agents.
Build and publish
CI (.github/workflows/test.yml) runs uv run pytest and smoke-builds the wrapper on every PR.
On merge to main, sync-claude.yml builds the wrapper and rsyncs it into
PolicyEngine/policyengine-claude — the marketplace repo users actually install — committing as
the sync bot. Build and test locally with:
uv run pytest # full lint + unit suite
python3 scripts/build_claude_wrapper.py --source-root . --output-root build/policyengine-claude
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.
- 4d ago First seen · 136 lines · 126 tokens per session scan C 07c496bb8d3b
policyengine-plugin-maintenance is a skill published in the GitHub repository PolicyEngine/policyengine-claude (32 stars, last pushed 2d ago), licensed MIT. It adds 126 tokens to every session and 1,776 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…