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 wahidyankf/ose-public --skill docs-authoring-standardsgit clone --depth 1 https://github.com/wahidyankf/ose-publicWrote 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/wahidyankf/ose-public/docs-authoring-standards)<a href="https://agentmods.dev/skills/wahidyankf/ose-public/docs-authoring-standards"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/docs-authoring-standards/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/wahidyankf/ose-public/docs-authoring-standards"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/docs-authoring-standards.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.00068 | $0.00406 |
| Opus 5.5 | $0.00027 | $0.00162 |
| Sonnet 5.5 | $0.00014 | $0.00081 |
| Haiku 4.5 | $0.00007 | $0.00041 |
Grade A, and why
docs-authoring-standards 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 2d 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.
What it actually says
Authoring Documentation Standards
Overview
This Skill packages the docs-maker agent's repository-specific authoring standards that
aren't covered by the universal quality/framework skills: how to verify accuracy before
publishing, the frontmatter template, and the distinct rules for editing AGENTS.md.
Reference Modules
- Verification and Correctness — the Documentation First principle, verification requirements per information type, and the pre-publish correctness checklist
- Frontmatter, Tags, and AGENTS.md Philosophy — the frontmatter template, date-field convention, tag usage, and the AGENTS.md navigation-document rules
Core Principles
- Correctness is non-negotiable — verify against source code, tests, and cited external sources rather than assumptions.
- AGENTS.md is navigation, not a knowledge dump — 3-5 line summaries with links; detail
lives in
repo-governance/conventions/orrepo-governance/development/. - Two-tier rule references: first mention links, subsequent mentions use inline code — see Linking Convention.
Related Skills
docs-applying-content-quality— universal active voice, heading hierarchy, accessibilitydocs-applying-diataxis-framework— the four documentation categories and their directoriesdocs-creating-accessible-diagrams— Mermaid diagram standards and accessible palette
What ships with it
4 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.
- 2d ago First seen · 37 lines · 68 tokens per session scan A 5f018a0045c7
docs-authoring-standards is a skill published in the GitHub repository wahidyankf/ose-public (12 stars, last pushed today), licensed MIT. It adds 68 tokens to every session and 406 once invoked, about $0.0003 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-10-14.
Other skills, from other repositories
turborepo
Configure and troubleshoot Turborepo repositories. Use when working with turbo.json, task pipelines, caching, Remote Cache, the turbo CLI, filtering, environment variables, package boundaries, monorepo structure, or CI workflows.
nx-plugin-for-aws
Scaffold and build cloud-native applications on AWS using @aws/nx-plugin generators. Use when the user wants to create workspaces, generate projects, or scaffold infrastructure with the Nx Plugin for AWS.
frontmcp-setup
Use when starting, scaffolding, or organizing a FrontMCP project. Covers creating a new project (CLI scaffold or manual) for Node, Vercel, and other targets; standalone versus Nx-monorepo layout, naming conventions, generators, and dependency rules; composing multiple @App classes, ESM packages, and remote MCP servers…
investigate-cloudflare
Investigate deployed Worker failures, regressions, and missing operational signals using Cloudflare Issues, logs, traces, SQL, or Observability MCP. Produce bounded evidence and verify recurrence against the deployed version.
add-a-lib
Scaffold a new shared library under libs/ in the builders-stack monorepo. Use when code is needed in two or more places (apps or services) and should become a single source of truth consumed by package name. Covers the package.json, tsconfig, the one-public-door src/index.ts barrel, and wiring it into a consumer…
implement
Implement an agreed issue or spec through implementation, review, fixes, and a PR ready to merge.