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 doodledood/manifest-dev --skill review-writinggit clone --depth 1 https://github.com/doodledood/manifest-devWrote 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/doodledood/manifest-dev/review-writing)<a href="https://agentmods.dev/skills/doodledood/manifest-dev/review-writing"><img src="https://agentmods.dev/badge/skills/doodledood/manifest-dev/review-writing/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/doodledood/manifest-dev/review-writing"><img src="https://agentmods.dev/badge/skills/doodledood/manifest-dev/review-writing.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.00103 | $0.01320 |
| Opus 5 | $0.00051 | $0.00660 |
| Sonnet 5 | $0.00021 | $0.00264 |
| Haiku 4.5 | $0.00010 | $0.00132 |
Grade A, and why
review-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 4d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
review-writing — review prose in its own register
Report where a text departs from the writing standard that governs it. Review only: you find and explain, the author decides and edits.
Input
$ARGUMENTS carries what to review — a file path, a directory, a glob, or pasted text. It may
also name a register explicitly (register=docs, register=voice) to override detection. A
manifest gate's body activates this skill with a register under the run's selected evaluator; the
gate names the register and this skill owns the threshold.
With no argument, review the most recently modified prose file in the working tree and say which one you picked. If that is ambiguous or nothing prose-shaped has changed, ask what to review rather than guessing.
Registers and thresholds
Two registers, mutually exclusive. Each has its own rules, and applying the wrong set produces findings the author should ignore — which costs more than reviewing nothing. The threshold is the bar a text must clear to PASS in that register:
| Register | What it covers | Rules | Threshold (PASS requires) |
|---|---|---|---|
docs |
Specs, proposals, reports, formal and technical documentation, READMEs, reference material, API docs | ../define/references/DOCS-STYLE-REFERENCE.md |
no MEDIUM-or-higher findings |
voice |
Articles, blog posts, marketing and social copy, newsletters, narrative, creative writing | ../define/references/WRITING-REFERENCE.md |
no MEDIUM-or-higher findings |
Each register brings the shared floor with it: ../define/references/PROSE-FLOOR-REFERENCE.md
holds the rules common to both, including the accessibility and inclusive-language floors, and a
finding from the floor is graded and reported on the same footing as one from the register. There
is no separate floor-only invocation.
The two thresholds sit at the same grade and still mean different things, because each register's severity anchor measures its own reader-facing cost — usability of documentation, or loss of meaning and intended voice in authored prose. Grade by the anchor of the register you applied, and never convert a finding from one scale to the other.
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.
- 4d ago Changed ac89f2354424
- 5d ago Changed b229aef0181c
- 10d ago First seen · 108 lines · 103 tokens per session scan A 1bbfb0394c88
review-writing is a skill published in the GitHub repository doodledood/manifest-dev (73 stars, last pushed 2d ago), licensed MIT. It adds 103 tokens to every session and 1,320 once invoked, about $0.0005 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.
Other skills, from other repositories
great_cto
Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.
skeptical-triage
Reusable 3-round self-challenge + arbiter pattern for filtering false positives from findings/verdicts. Use when the cost of a false-positive gate block exceeds the cost of 4 extra LLM turns.
vertical-real-estate
Residential-proptech domain knowledge so architect / pm aren't naive when speccing real-estate products (listings, lead-crm, transaction-coordination, property-mgmt). Codifies MLS/IDX reality, listing status lifecycle + syndication canonical-source, long-cycle lead nurture, transaction-coordination as the high-pain…
product-economics
Does this product make money at a price someone will pay? Forces contribution margin, a price with a stated basis, and a bottom-up market size — each number labelled measured / assumed / unknown, so a guess can never be read as a calculation.
anti-patterns
Catalogue of known SDLC anti-patterns that greatcto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).
cost-model
Standardized cost-estimation framework for greatcto plans. Forces explicit LLM cost, infra cost, human-supervision time, and the (defensible) human-equivalent comparison. Output format is parsable by the board's /api/cost path — must follow exactly.