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/rse/ase/ase-docs-proofreadnpx skills add rse/ase --skill ase-docs-proofreadgit clone --depth 1 https://github.com/rse/aseWhat 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.00036 | $0.03805 |
| Opus 5 | $0.00018 | $0.01903 |
| Sonnet 5 | $0.00007 | $0.00761 |
| Haiku 4.5 | $0.00004 | $0.00380 |
Grade A, and why
ase-docs-proofread 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 — 364 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md @${CLAUDE_SKILL_DIR}/../../meta/ase-dialog.md @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
$ARGUMENTS
-
The project source artifacts are classified as a black box, so the user does not want them inspected or their problems surfaced. Skip the entire investigation and reporting: do not invoke any
GloborAgenttool and do not read any document, only output the following and then SKIP the remaining steps STEP 2 and STEP 3:First, use the following to give a hint on this step:
Dispatch the investigation to sub-agents via the
Agenttool so that no investigation details leak into the user-visible transcript. The sub-agents perform the silent reading and checking; only their final structured return values are consumed here.For this, first silently resolve
<getopt-arguments/>to the list of individual document files, expanding any directory or wildcard references with theGlobtool. Then partition , preserving order, into at most eight batches of roughly equal size (a single document yields a single batch), and invoke the following tool once per batch, emitting all invocations in one single message so they run in parallel:Agent( description: "Proofread Investigation (<batch-index/>/<batch-count/>)", subagent_type: "ase:ase-docs-proofread", prompt: <batch/>, run_in_background: false )Here is the space-separated list of the document file paths of the corresponding batch, is the 1-based index of that batch, and is the total number of batches, so that each parallel invocation is distinguishable in the progress display.
Parse the result message of each
Agenttool invocation as a JSON array, concatenate all those arrays, sort the combined list byfileand then numerically byline, and set to that list.You MUST NOT output anything at all in this STEP 1 beyond the above hint template and the
GlobandAgenttool invocations. -
Use the following to give a summary of the detected problems in :
Proofread Type Proofread Result SPELLING: problems found PUNCTUATION: problems found GRAMMAR: problems found Hints:
- is the number of problems with
typeequal toSPELLINGin - is the number of problems with
typeequal toPUNCTUATIONin - is the number of problems with
typeequal toGRAMMARin
- is the number of problems with
-
- Mark this skill as the active edit-capable skill so that the
ASE
pre-tool-usehook auto-approves the subsequentEditinvocations on any invocation path (slash command orSkilltool). Call thease_config_set(key: "agent.skill", val: "ase-docs-proofread", scope: "session:<ase-session-id/>")tool from theaseMCP server. Do not output anything in this substep.
- Mark this skill as the active edit-capable skill so that the
ASE
What ships with it
1 file 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 First seen · 364 lines · 36 tokens per session scan A 95ac1b45d02b
ase-docs-proofread is a skill published in the GitHub repository rse/ase (47 stars, last pushed 5d ago), licensed Apache-2.0. It adds 36 tokens to every session and 3,805 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-08-30.
Other skills, from other repositories
moai-workflow-project
Integrated project management system covering documentation, language initialization, template optimization, docs generation, and JIT document loading. Absorbed from moai-workflow-templates, moai-docs-generation, and moai-workflow-jit-docs.
ospec
Document-driven OSpec workflow for initialization, change/goal routing, validation, archiving, and durable project knowledge.
moai-domain-html-report
Markdown-to-single-file-HTML report renderer. Six modes (status, incident, plan, explainer, financial, pr) selected by report type, crossed with three audience tiers (expert, basic, learn) derived from the active output style. The basic and learn tiers enrich the HTML with mermaid flowcharts, worked examples, and…
ai-provider-claude-vision
Image understanding and document analysis with Claude's multimodal capabilities -- image input formats, PDF processing, multi-image patterns, structured extraction, and token cost estimation.
author-product-docs
Create, revise, retrofit, audit, or verify product documentation — pack READMEs, journeys, tutorials, how-to guides, reference pages, and explanations. Use when asked to write, improve, restructure, audit, or verify user-facing documentation, fix a pack README, create a guide for a feature, update a journey page, or…
summarize
Summarize or extract text and transcripts from URLs, podcasts, YouTube videos, and local files. Use when the user asks to summarize a link, article, or document, transcribe a YouTube video, or wants to know what a URL or video is about.