documents

A guide for creating reports, articles, notes, and other text documents with researched content and a clear structure.

In plain words
What is it for?
Use it to produce structured written documents for a specific purpose and format, with fact checking and a final save check.
Why use it?
It helps organize information into a complete document with an introduction, main sections, examples where useful, and conclusions.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/tripleguard/vera/documents
Any agent
npx skills add tripleguard/Vera --skill documents
Clone the repo
git clone --depth 1 https://github.com/tripleguard/Vera

Made for: Claude Code, Codex.

Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 253 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00023 $0.00253
Opus 5 $0.00012 $0.00127
Sonnet 5 $0.00005 $0.00051
Haiku 4.5 $0.00002 $0.00025

Measured 2d ago against content hash 4f11ed89832e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

skills/documents/SKILL.md · 19 lines

What it actually says

Создание текстового документа

  1. Определи тему, назначение и явно запрошенный формат документа.
  2. Если интернет доступен, собери актуальные сведения по нескольким узким запросам. Если поиск не дал данных, используй локальные знания и не выдумывай точные цифры.
  3. Сначала выстрой структуру: заголовок, введение, основные разделы, выводы. Для доклада или отчета добавь практические примеры и ограничения, когда они уместны.
  4. Пиши связный, самостоятельный текст, а не план и не несколько коротких тезисов.
  5. Не описывай процесс работы внутри документа и не упоминай инструменты.
  6. После сохранения проверь успешный результат инструмента. В финальном ответе сообщи, что документ создан, укажи формат и фактический путь.
  7. Не вызывай создание документа повторно после успешного сохранения.
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. 2d ago First seen · 19 lines · 23 tokens per session scan A 4f11ed89832e

Subscribe to this mod's changes

documents is a skill published in the GitHub repository tripleguard/Vera (135 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 253 once invoked, about $0.0001 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.

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

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

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

agent-host-chat-contributions

Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.

microsoft/vscode · 56 tokens