policyengine-writing

policyengine-writing is a skill for Claude Code, Codex from PolicyEngine/policyengine-claude. It costs 147 tokens per session (5,454 once invoked), scanned A, original, MIT.

A writing guide for public-facing PolicyEngine content, including research, documentation, reports, and announcements. PolicyEngine is a nonpartisan organization that analyzes taxes and public benefits.

In plain words
What is it for?
Use it when writing PolicyEngine reports, blog posts, documentation, pull-request descriptions, newsletters, READMEs, or social posts.
Why use it?
It keeps explanations clear, precise, neutral, and consistent. The guidance helps writers describe policy effects without turning analysis into unsupported recommendations.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/policyengine/policyengine-claude/policyengine-writing
Any agent
npx skills add PolicyEngine/policyengine-claude --skill policyengine-writing
Clone the repo
git clone --depth 1 https://github.com/PolicyEngine/policyengine-claude

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for policyengine-writing

README.md
[![agentmods](https://agentmods.dev/badge/skills/policyengine/policyengine-claude/policyengine-writing.svg)](https://agentmods.dev/skills/policyengine/policyengine-claude/policyengine-writing)
Your own site
<a href="https://agentmods.dev/skills/policyengine/policyengine-claude/policyengine-writing"><img src="https://agentmods.dev/badge/skills/policyengine/policyengine-claude/policyengine-writing.svg" alt="Measured on agentmods" height="20"></a>
Per session 147 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,454 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00147 $0.05454
Opus 5 $0.00073 $0.02727
Sonnet 5 $0.00029 $0.01091
Haiku 4.5 $0.00015 $0.00545

Measured 3d ago against content hash ae9be912393f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

policyengine-writing 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.

skills/policyengine-writing/SKILL.md · 741 lines

How it starts

The opening of the file, as written. The whole thing — 741 lines — stays where its author put it; the contents beside it link to each section on GitHub.

PolicyEngine Writing Skill

Use this skill when writing blog posts, documentation, PR descriptions, research reports, or any public-facing PolicyEngine content.

When to Use This Skill

  • Writing blog posts about policy analysis
  • Creating PR descriptions
  • Drafting documentation
  • Writing research reports
  • Composing social media posts
  • Creating newsletters
  • Writing README files

Core Principles

PolicyEngine's writing emphasizes clarity, precision, and objectivity.

  1. Active voice - Prefer active constructions over passive
  2. Direct and quantitative - Use specific numbers, avoid vague adjectives/adverbs
  3. Sentence case - Use sentence case for headings, not title case
  4. Neutral tone - Describe what policies do, not whether they're good or bad
  5. Precise language - Choose exact verbs over vague modifiers

Active Voice

Active voice makes writing clearer and more direct.

✅ Correct (Active):

Harris proposes expanding the Earned Income Tax Credit
The reform reduces poverty by 3.2%
PolicyEngine projects higher costs than other organizations
We estimate the ten-year costs
The bill lowers the state's top income tax rate
Montana raises the EITC from 10% to 20%

❌ Wrong (Passive):

The Earned Income Tax Credit is proposed to be expanded by Harris
Poverty is reduced by 3.2% by the reform
Higher costs are projected by PolicyEngine
The ten-year costs are estimated
The state's top income tax rate is lowered by the bill
The EITC is raised from 10% to 20% by Montana

Quantitative and Precise

Replace vague modifiers with specific numbers and measurements.

✅ Correct (Quantitative):

Costs the state $245 million
Benefits 77% of Montana residents
Lowers the Supplemental Poverty Measure by 0.8%
Raises net income by $252 in 2026
The reform affects 14.3 million households
Hours worked falls by 0.27%, or 411,000 full-time equivalent jobs
The top decile receives an average benefit of $1,033
PolicyEngine projects costs 40% higher than the Tax Foundation

Read the full file on GitHub · 741 lines

Changes

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.

  1. 3d ago First seen · 741 lines · 147 tokens per session scan A ae9be912393f

Subscribe to this mod's changes

policyengine-writing is a skill published in the GitHub repository PolicyEngine/policyengine-claude (32 stars, last pushed yesterday), licensed MIT. It adds 147 tokens to every session and 5,454 once invoked, about $0.0007 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-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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.

obra/superpowers · 37 tokens

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.

microsoft/vscode · 62 tokens

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.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens