docs-page-authoring

docs-page-authoring is a skill for Claude Code, Codex from Netcracker/qubership-ai-packages. It costs 221 tokens per session (6,989 once invoked), scanned B, original, Apache-2.0.

A set of rules for writing or editing documentation pages in a code repository. It defines what each kind of page should say, who it serves, and what it must not claim.

In plain words
What is it for?
Use it for READMEs, reference and options pages, feature pages, how-to guides, tutorials, troubleshooting pages, and migration guides, especially when a code change adds or changes an option.
Why use it?
Documentation can be accurate but still fail readers if information appears in the wrong order or answers the wrong question. These rules keep the page focused on the reader's task while leaving wording and layout to the appropriate tools.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it for READMEs, reference and options pages, feature pages, how-to guides, tutorials, troubleshooting pages, and migration guides, especially when a code change adds or changes an option.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/netcracker/qubership-ai-packages/docs-page-authoring
Install

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.

Any agent
npx skills add Netcracker/qubership-ai-packages --skill docs-page-authoring
Clone the repo
git clone --depth 1 https://github.com/Netcracker/qubership-ai-packages

Made for: Claude Code, Codex.

Its marketplace also offers this one on its own, as the plugin docs-page-authoring/plugin install docs-page-authoring after adding the marketplace above.

Wrote 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.

agentmods badge for docs-page-authoring

README.md
[![agentmods](https://agentmods.dev/badge/skills/netcracker/qubership-ai-packages/docs-page-authoring/github.svg)](https://agentmods.dev/skills/netcracker/qubership-ai-packages/docs-page-authoring)
Your own site
<a href="https://agentmods.dev/skills/netcracker/qubership-ai-packages/docs-page-authoring"><img src="https://agentmods.dev/badge/skills/netcracker/qubership-ai-packages/docs-page-authoring/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.

agentmods 80×15 button for docs-page-authoring

Your own site · 80×15
<a href="https://agentmods.dev/skills/netcracker/qubership-ai-packages/docs-page-authoring"><img src="https://agentmods.dev/badge/skills/netcracker/qubership-ai-packages/docs-page-authoring.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 221 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,989 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00221 $0.06989
Opus 5 $0.00111 $0.03495
Sonnet 5 $0.00044 $0.01398
Haiku 4.5 $0.00022 $0.00699

Measured 7d ago against content hash b68881e4c799, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade B, and why

docs-page-authoring scanned grade B with 1 finding 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.

Subtle steeringmediumPrompt injection

Instructions that bias recommendations or shape behaviour without the user noticing.

this sentence stop being true without any user noticing a behavior change?* If it could, it describes the
agent-packages/docs-page-authoring/.apm/skills/docs-page-authoring/SKILL.md · 393 lines

How it starts

The opening of the file, as written. The whole thing — 393 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Authoring a documentation page

This skill governs what a page says, for whom, in what order, and what it may not claim. Wording, tone, sentence length, and dialect belong to english-developer-style; load it too, and let it own the sentences. The changelog entry and the pull request description belong to change-description-authoring. Layout a linter settles, such as line length, one H1, named links, and a language tag on every fence, belongs to the repository's markdownlint configuration.

A page is not read; a section is, by a reader who arrived with a question and leaves when it is answered. Every rule below names that reader, because the same sentence is essential to one reader and noise to another, and the only way to decide is to ask whose question it answers.

1. The correction that matters most

Write from the reader's seat, not the author's. The author has just finished understanding the code and wants to explain it: how the mechanism works, why the design is right, what changed since last time. None of the readers below asked that. Each holds one thing and brings one question, and a section earns its place by answering it.

Reader Holds Opens Asks
D1 Evaluator A requirement, a comparison README, landing page What is this? Does it do X? What does trying it cost?
D2 First-time integrator An empty project Getting-started page, tutorial What is the shortest path to something that works?
D3 Task-doer A goal in the product's terms Feature page, how-to guide How do I do X? What do I set, call, or run?
D4 Configurer A config file, a connection string, a requirement (memory, latency, a limit) The reference entry for one option What does it control? Default, syntax, scope? What happens at the limit? How does it interact with Y?
D5 Troubleshooter An error message, an exception, a log line, a wrong result Whatever a web search on the literal text returns What does this mean? What causes it? What do I change?
D6 Upgrader Two versions Migration guide, version markers, changelog What changed that I can observe? Must I act?
D7 Contributor A clone and a build Development and contributing pages How do I build, test, and submit?

Read the full file on GitHub · 393 lines

Changes

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.

  1. 7d ago First seen · 393 lines · 221 tokens per session scan B b68881e4c799

Subscribe to this mod's changes

docs-page-authoring is a skill published in the GitHub repository Netcracker/qubership-ai-packages (4 stars, last pushed 2d ago), licensed Apache-2.0. It adds 221 tokens to every session and 6,989 once invoked, about $0.0011 per session on Opus 5. A static security scan graded it B with 1 finding (subtle steering). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-05.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens