kendex: Skill for Claude Code

.agents/skills/docs-writing/SKILL.md

docs-writing is a skill for Claude Code from vanillagreencom/kendex. It costs 35 tokens per session (5,198 once invoked), scanned C, original, MIT.

Writing guidance for repository-owned Markdown files such as READMEs, architecture notes, and agent instructions. It sets rules for short, clear statements and for recording decisions, boundaries, and proof.

In plain words
What is it for?
It helps write, rewrite, and review project documentation, reference pages, development guides, and agent instruction files.
Why use it?
It prevents documentation from duplicating source files or making unsupported claims about what tools enforce.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions Claude Code.

This is vanillagreencom/kendex's own configuration. It tells Claude Code how to work on kendex itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything kendex configures →

Reuse

Borrowing it

Nothing to install: this file belongs to vanillagreencom/kendex. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/vanillagreencom/kendex/main/.agents/skills/docs-writing/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/vanillagreencom/kendex

Made for: Claude Code.

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-writing

README.md
[![agentmods](https://agentmods.dev/badge/skills/vanillagreencom/kendex/docs-writing/github.svg)](https://agentmods.dev/skills/vanillagreencom/kendex/docs-writing)
Your own site
<a href="https://agentmods.dev/skills/vanillagreencom/kendex/docs-writing"><img src="https://agentmods.dev/badge/skills/vanillagreencom/kendex/docs-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.

agentmods 80×15 button for docs-writing

Your own site · 80×15
<a href="https://agentmods.dev/skills/vanillagreencom/kendex/docs-writing"><img src="https://agentmods.dev/badge/skills/vanillagreencom/kendex/docs-writing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,198 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 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.00035 $0.05198
Opus 5.5 $0.00014 $0.02079
Sonnet 5.5 $0.00007 $0.01040
Haiku 4.5 $0.00003 $0.00520

Measured 8d ago against content hash e6f86242f351, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

docs-writing scanned grade C 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 8d 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.

Hidden instructionshighPrompt injection

Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.

<!-- kendex:project-instructions:start -->
.agents/skills/docs-writing/SKILL.md · 204 lines

How it starts

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

Project Instructions

Problems with a kendex-owned skill go through kendex report; check ownership in the file first.

After an authorized documentation rewrite changes kendex-owned inputs, use the repository refresh and verification route. Respect a launched lane's refresh restriction. Keep refresh with the existing owner: kendex uses its lock-record Actions workflow and rolling kendex/lock pull request; consumers with automatic refresh use their kendex-refresh Actions workflow and rolling kendex/refresh pull request. When no refresh workflow exists and the fleet is local, the overseer owns refresh in the base checkout. Keep the local-fleet full post-merge route. This local owner is not a hosted control VM. Confirm any other execution owner before adoption. A hosted consumer without a refresh workflow must confirm an authorized owner outside the control VM. The hosted control checkout receives committed outputs through sync-base after they merge.

Migrate this repository hand-written harness instructions only through an authorized instruction migration. Put rules used by one installed skill in that skill's named [skill-instructions] key in kendex.toml, or kendex-local.toml only for a source catalog. Put agent-specific rules in the named [agent-additional-instructions] key and command-specific rules in the named [command-instructions] key. Keep only rules every agent needs in AGENTS.md. Keep operator instructions in consumer docs. Preserve every still-required rule. Remove an empty source instruction file only after its replacement is checked.

Docs Writing

A repository's internal design documentation holds what the code cannot show: the principle behind a design, the rule an agent could break without noticing, a decision with its reason, a convention that differs from a tool default, and a pointer to the canonical code. Everything else lives in the code, its comments, the tests and git history.

Read the full file on GitHub · 204 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. 8d ago Changed · -5 lines e6f86242f351
  2. 14d ago Changed 411a9130f92c
  3. 17d ago Changed · +10 lines 3702b80c0447
  4. 19d ago Changed · +4 lines be281f04d193
  5. 20d ago Changed · -1 lines 93e5c78d7ff5
  6. 21d ago Changed · +1 lines e977d83ebcc7
  7. 22d ago Changed · +21 lines e3c84582d8a7
  8. 23d ago Changed · +1 lines 65caeef4f96d
  9. 25d ago Changed 69d6e3962d3f
  10. 1mo ago First seen · 173 lines · 35 tokens per session scan C 54fcf77f3e90

Subscribe to this mod's changes

docs-writing is a skill published in the GitHub repository vanillagreencom/kendex (87 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 5,198 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-06.