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 attilaszasz/sdd-pilot --skill writing-qualitygit clone --depth 1 https://github.com/attilaszasz/sdd-pilotWrote 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/attilaszasz/sdd-pilot/writing-quality)<a href="https://agentmods.dev/skills/attilaszasz/sdd-pilot/writing-quality"><img src="https://agentmods.dev/badge/skills/attilaszasz/sdd-pilot/writing-quality/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/attilaszasz/sdd-pilot/writing-quality"><img src="https://agentmods.dev/badge/skills/attilaszasz/sdd-pilot/writing-quality.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.00035 | $0.01377 |
| Opus 5 | $0.00017 | $0.00688 |
| Sonnet 5 | $0.00007 | $0.00275 |
| Haiku 4.5 | $0.00003 | $0.00138 |
Grade A, and why
writing-quality 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 7d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing quality
Runtime primer:
AGENTS.mdsectionCommunication StyleunderWriting Quality. This file expands the editing rules and safety limits. It is not a required read during ordinary workflow execution.
Adapted from the user-provided Unslop rules.
Purpose
Edit prose so it sounds direct, specific, and written for this project. Remove stock AI phrasing without making the text sterile or changing what it claims.
Preserve meaning, scope, certainty, evidence, citations, and the user's voice. Style work never authorizes a new requirement, stronger claim, resolved ambiguity, changed priority, or removed caveat.
Process
- Scan newly written or changed prose for the patterns below.
- Rewrite only the affected narrative spans. Match the intended tone.
- Add human judgment where the format allows it. Be specific, vary sentence length, and use first person when it fits.
- Ask, "What makes this obviously AI generated?" Fix any remaining tells.
- Run the owning structural validator after the writing pass.
Safety limits
Never run a whole-file style rewrite over SDDP artifacts or governance files. In parser-sensitive files, edit only narrative spans created or changed by the current task.
Preserve these elements exactly unless the workflow explicitly owns their change:
- frontmatter, headings, required section order, tables, and column schemas
- checkbox lines and state
- IDs, priorities, markers, tags, paths, commands, URLs, and citations
- code fences, inline code, Mermaid, JSON, JSONL, YAML, OpenAPI, and GraphQL
- quoted user or source text
- uncertainty and legal, security, policy, or compliance language
- append-only history in
autopilot-log.mdanddivergence-log.md
Do not use writing quality to resolve [NEEDS CLARIFICATION], alter acceptance criteria, reorder priorities, or mutate artifact grammars. ADR files remain writable only through the ADR Author.
If deterministic Markdown compression also applies, use this order:
- Complete the writing-quality pass.
- Run validator-backed Markdown compression.
- Run the artifact's structural validator.
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.
- 7d ago First seen · 105 lines · 35 tokens per session scan A 3d8977d7ee95
writing-quality is a skill published in the GitHub repository attilaszasz/sdd-pilot (96 stars, last pushed 6d ago), licensed MIT. It adds 35 tokens to every session and 1,377 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
universal-live-check
Universal live-check framework for coding agents. Executes incremental, deterministic validation across all software domains (CLI, backend, frontend, mobile, embedded, libs). Change-type-aware (feat, fix, hotfix, refactor, migrate, docs). Triggers whenever an agent needs to validate code quality, run linting, perform…
code-review-hardening
Use this skill for rigorous, structured code review with a self-repair loop. Applies change-type-aware strategies (feat, fix, hotfix, refactor, migrate, docs). Findings are severity-classified, then auto-fixed where possible. Triggers on PR reviews, code review requests, or when reviewing any change set.
contextual-stewardship
Use this skill when the user makes a technical decision, establishes a new pattern, defines business rules, or explicitly asks to remember or save a guideline. Also use this skill when you are about to implement a feature, write code, plan an architecture, or make a technical decision - you MUST retrieve contextual…
project-guidelines-writer
Use this skill when the user wants repository guidance documents generated or refreshed, including AGENTS.md, CONTRIBUTING.md, STYLEGUIDE.md, TESTING.md, ARCHITECTURE.md, and SECURITY.md. It analyzes the repository, generates all six guideline files by default, prefers managed-section updates for existing files, and…
quality-grading
Use this skill to grade code, specifications, or design documents across four quality dimensions using a 1-5 scoring scale. In grade-and-fix mode, the skill auto-improves artifacts scoring below 5 without prompting. Invoke when you want consistent quality assessment on design, implementation, or specification with…
spec-driven-task-decomposer
Use this skill when approved requirements and design need to be decomposed into tasks.md for Phase 3 of a Spec-Driven change. It creates atomic, traceable implementation and testing tasks, validates the plan, and should not be used to design architecture or write implementation code.