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 peteromallet/Arnold --skill writing_panel_strictgit clone --depth 1 https://github.com/peteromallet/ArnoldWrote 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/peteromallet/arnold/writing_panel_strict)<a href="https://agentmods.dev/skills/peteromallet/arnold/writing_panel_strict"><img src="https://agentmods.dev/badge/skills/peteromallet/arnold/writing_panel_strict/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/peteromallet/arnold/writing_panel_strict"><img src="https://agentmods.dev/badge/skills/peteromallet/arnold/writing_panel_strict.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.00023 | $0.00625 |
| Opus 5.5 | $0.00009 | $0.00250 |
| Sonnet 5.5 | $0.00005 | $0.00125 |
| Haiku 4.5 | $0.00002 | $0.00063 |
Grade A, and why
writing-panel-strict 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Panel (Strict)
A multi-reviewer pipeline for rigorous prose revision. Three independent reviewers (pessimist, optimist, structuralist) critique a draft in parallel, a synthesis editor reconciles their feedback into a revision brief, and a revision editor produces the updated draft. A human gate lets you review the result and loop back for another round or stop.
Runtime
writing-panel-strict is a native-default converted pipeline. Fresh runs
through megaplan run writing-panel-strict ... or
arnold pipelines run writing-panel-strict ... persist runtime ownership in
state.json.runtime_envelope.runtime and state.json.meta.executor. During
the M7 deprecation window, the derived graph remains available as a
compatibility fallback: pass --runtime graph (or the deprecated
--executor graph) for a fresh run that must use the graph executor. Existing
graph-born plan directories keep resuming on graph. Native-born runs resume on
native, and corrupt native cursors fail closed rather than silently falling
back to graph.
Modes
| Mode | Description |
|---|---|
polish |
Light editing — tighten prose, fix errors, preserve structure |
restructure |
Reorganize sections, improve flow, may move content |
provoke |
Push the draft to be bolder, more opinionated, less safe |
Inputs
draft(file, required): Path to the markdown draft to review.
Usage
# Run with default profile
megaplan run writing-panel-strict path/to/draft.md
# Run with a specific mode
megaplan run writing-panel-strict path/to/draft.md --mode polish
# Run with a specific profile
megaplan run writing-panel-strict path/to/draft.md --profile @writing-panel-strict:standard
# Resume after human gate
megaplan resume <plan-dir> --choice continue
megaplan resume <plan-dir> --choice stop
Pipeline Flow
- Panel Review (parallel) — pessimist, optimist, and structuralist review the draft independently.
- Synthesis — editor reconciles the three reviews into a revision brief.
- Revise — editor rewrites the draft incorporating the revision brief.
- Human Gate — you inspect the revised draft. Choose
continueto loop back for another round, orstopto finish.
What ships with it
9 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.
- 1mo ago First seen · 70 lines · 23 tokens per session scan A 8683726063ac
writing-panel-strict is a skill published in the GitHub repository peteromallet/Arnold (98 stars, last pushed yesterday), licensed Apache-2.0. It adds 23 tokens to every session and 625 once invoked, about $0.0001 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-04.
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…