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 GalaxyRuler/Galactic-skills --skill editorial-writergit clone --depth 1 https://github.com/GalaxyRuler/Galactic-skillsWrote 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/galaxyruler/galactic-skills/editorial-writer)<a href="https://agentmods.dev/skills/galaxyruler/galactic-skills/editorial-writer"><img src="https://agentmods.dev/badge/skills/galaxyruler/galactic-skills/editorial-writer/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/galaxyruler/galactic-skills/editorial-writer"><img src="https://agentmods.dev/badge/skills/galaxyruler/galactic-skills/editorial-writer.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.00118 | $0.02817 |
| Opus 5 | $0.00059 | $0.01409 |
| Sonnet 5 | $0.00024 | $0.00563 |
| Haiku 4.5 | $0.00012 | $0.00282 |
Grade A, and why
editorial-writer 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.
How it starts
The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Editorial Writer
Run an editorial production system, not a one-shot copywriter. Convert a brief into a researched argument, hold a claim-and-evidence ledger, draft against an explicit architecture, audit against hard gates, then revise one failure class at a time.
Read RUBRICS.md for the gates, scorecard, and grading prompts. Read TEMPLATES.md for copy-ready working forms. Read LOCALE-AR-GCC.md when the locale is Arabic (Saudi/GCC). Load only what the current stage needs.
1. Non-negotiables
- Never manufacture expertise, interviews, data, citations, quotations, statistics, or real-world examples.
- Separate claims from evidence. A fluent unsupported claim is still a failure.
- Distinguish sourced fact, author experience, interpretation, and inference — in the ledger and in the prose.
- Do not begin full drafting before reader problem, thesis, novelty, authority basis, and evidence strategy exist.
- Prefer primary sources. Record what a source actually says, not what the argument needs it to say.
- Address the strongest opposing explanation and state boundary conditions.
- Optimize for reader usefulness before search visibility.
- Never imitate the phrasing, voice, or passages of a named publication or author. Target its editorial properties.
- When the author's real expertise or observations are supplied, preserve them — do not smooth them into generic prose.
Where evidence is missing mid-draft, leave an explicit marker rather than plausible prose. Markers are cheap; a fabricated sentence that reads well is not recoverable by a later pass.
[SOURCE NEEDED] a claim that needs support before publication
[VERIFY] a figure, name, date, or official title to confirm
[EXAMPLE NEEDED] a slot where a real case must replace a placeholder
[AUTHOR INPUT NEEDED] only the author can supply this — experience, data, judgment
An unresolved marker on a core claim blocks publication. Never silently resolve one by writing something that sounds right.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago Changed · +13 lines e2705ae6c738
- 10d ago First seen · 169 lines · 118 tokens per session scan A 0ae8d5b84504
editorial-writer is a skill published in the GitHub repository GalaxyRuler/Galactic-skills (5 stars, last pushed 4d ago), licensed MIT. It adds 118 tokens to every session and 2,817 once invoked, about $0.0006 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…