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/pekral/cursor-rules/article-writingnpx skills add pekral/cursor-rules --skill article-writinggit clone --depth 1 https://github.com/pekral/cursor-rulesWhat 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.00057 | $0.00738 |
| Opus 5 | $0.00028 | $0.00369 |
| Sonnet 5 | $0.00011 | $0.00148 |
| Haiku 4.5 | $0.00006 | $0.00074 |
Grade A, and why
article-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 2d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Article Writing
Write long-form content that sounds like an actual person with a point of view, not an LLM smoothing itself into paste.
Constraints
- Output must be in the language the user requests; default to English when unspecified.
- Never invent facts, credibility, statistics, or customer evidence.
- Match the supplied voice; do not impose a house style over clear examples.
- Do not add marketing links, calls to action, or third-party promotion unless asked.
Use when
- Drafting blog posts, essays, launch posts, guides, tutorials, or newsletter issues
- Turning notes, transcripts, or research into polished articles
- Matching an existing founder, operator, or brand voice from examples
- Tightening structure, pacing, and evidence in already-written long-form copy
Core Rules
- Lead with the concrete thing: artifact, example, output, anecdote, number, screenshot, or code.
- Explain after the example, not before.
- Keep sentences tight unless the source voice is intentionally expansive.
- Use proof instead of adjectives.
- Never invent facts, credibility, or customer evidence.
Voice Handling
If the user supplies voice examples, derive a short voice profile first (do not skip this):
- Sentence length and rhythm (short and punchy vs. expansive)
- Vocabulary register (technical, casual, formal) and recurring phrases
- Point of view (first / second / third person) and level of opinion
- Formatting habits (headers, lists, code, em-dashes)
Reuse that profile consistently across the whole piece. If no voice references are given, default to a sharp operator voice: concrete, unsentimental, useful.
Banned Patterns
Delete and rewrite any of these:
- "In today's rapidly evolving landscape"
- "game-changer", "cutting-edge", "revolutionary"
- "here's why this matters" as a standalone bridge
- fake vulnerability arcs
- a closing question added only to juice engagement
- biography padding that does not move the argument
- generic AI throat-clearing that delays the point
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.
- 2d ago First seen · 82 lines · 57 tokens per session scan A b0d9848fc592
article-writing is a skill published in the GitHub repository pekral/cursor-rules (6 stars, last pushed 8d ago), licensed MIT. It adds 57 tokens to every session and 738 once invoked, about $0.0003 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-31.
Other skills, from other repositories
migrate-radix-to-base
Migrates React projects and components from Radix UI to Base UI. Use when asked to migrate from radix, move to base-ui, convert radix primitives, or switch a shadcn project's base library. Handles single components ("migrate accordion") and whole projects.
ponytail-gain
Show ponytail measured impact as a scoreboard: less code, less cost, more speed, from the benchmark medians. One-shot display.
parse-table
Parse table definition to extract module name, model name, table name, and field definitions. First step of CRUD generation.
owl-admin-ops-commands
Use this skill for Owl Admin installation, publishing assets, upgrades, diagnostics, database inspection, menu maintenance, user creation, password reset, route generation, IDE helper, admin:publish, admin:install, admin:update, admin:doctor, admin:db, admin:menu, admin:create-user, or deployment troubleshooting.
octane-development
Use this skill when working with Laravel Octane, a long-running PHP worker server (Swoole, FrankenPHP, RoadRunner) where the application boots once and serves many requests instead of rebooting for each request like PHP-FPM. Trigger when installing Octane or starting its server; configuring or detecting the active…
module:assistant
Add an AI assistant chat panel to any Laravel project — with tool calling, streaming, and MCP support.