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 adilkalam/orca --skill pg-style-editorgit clone --depth 1 https://github.com/adilkalam/orcaWrote 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/adilkalam/orca/pg-style-editor)<a href="https://agentmods.dev/skills/adilkalam/orca/pg-style-editor"><img src="https://agentmods.dev/badge/skills/adilkalam/orca/pg-style-editor/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/adilkalam/orca/pg-style-editor"><img src="https://agentmods.dev/badge/skills/adilkalam/orca/pg-style-editor.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.00061 | $0.03287 |
| Opus 5.5 | $0.00024 | $0.01315 |
| Sonnet 5.5 | $0.00012 | $0.00657 |
| Haiku 4.5 | $0.00006 | $0.00329 |
Grade A, and why
pg-style-editor 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 — 440 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PG Style Editor (Research & Long-Form)
Apply Paul Graham's writing principles to make research and long-form content clearer, more concrete, and more engaging.
Based on analysis of 35 Paul Graham essays - including long-form research on economics, philosophy, systems analysis, and analytical frameworks.
When to Use This Skill
Use when the user:
- Says "edit this in Paul Graham's style"
- Says "make this clearer"
- Says "simplify this writing"
- Says "make this more conversational"
- Asks to "rewrite this like PG"
- Wants to apply PG's writing principles
Keywords to watch for: Paul Graham, PG style, clearer, simpler, more concrete, conversational, accessible
The 10 Core PG Principles
1. Sentence Rhythm: Varied for Emphasis
Pattern: Short sentences after long ones create impact.
Bad (monotonous):
We need to consider the implications of this decision. This decision will affect our entire organization. The organization has many stakeholders. The stakeholders all have different priorities.
Good (varied rhythm):
This decision affects everyone. Our stakeholders have competing priorities, from customers who want features shipped fast to investors who want profitability. Which matters most? Growth.
Rules:
- Mix short (3-7 words), medium (10-20), and long (20+) sentences
- Use short sentences for key claims
- Fragments are allowed for emphasis: "Not anymore." "Exactly."
2. Word Choice: Simple, Concrete, Active
Pattern: Germanic words over Latinate. Concrete over abstract.
Bad:
We utilized advanced methodologies to facilitate optimization of the user experience and enhance customer satisfaction metrics.
Good:
We fixed the bugs users complained about most.
Rules:
- "use" not "utilize"
- "help" not "facilitate"
- "show" not "demonstrate"
- Prefer physical metaphors: "shaking bins," "gravitational field," "car spinning its wheels"
- Active voice: "Founders make startups take off" not "Startups are grown by founders"
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 · 440 lines · 61 tokens per session scan A 081296bf8396
pg-style-editor is a skill published in the GitHub repository adilkalam/orca (2 stars, last pushed 2mo ago), licensed MIT. It adds 61 tokens to every session and 3,287 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-03.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…