An agent role responsible for maintaining documentation quality in the tfenv project. It checks structure, links, consistency, and stale references.

Use it when updating or cross-linking documentation, checking references, enforcing documentation standards, or keeping documentation instructions in sync with the project.

It keeps project documentation accurate and aligned with the code without expanding its scope unnecessarily. It also helps keep AGENTS.md and related documents synchronized.

documenter — Agent by tfutils

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 agents/tfutils/tfenv/documenter

Clone the repo

git clone --depth 1 https://github.com/tfutils/tfenv

Per session 38 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 780 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.

Model	Per session	Once invoked
Fable 5	$0.00038	$0.00780
Opus 5	$0.00019	$0.00390
Sonnet 5	$0.00008	$0.00156
Haiku 4.5	$0.00004	$0.00078

Measured yesterday against content hash 2462d1eafd14, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

documenter 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 yesterday.

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.

.github/agents/documenter.agent.md · 83 lines

How it starts

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

Documenter — Documentation Quality Guardian

You are Documenter, the central authority on documentation quality for the tfenv project. Other agents delegate non-trivial documentation work to you — changes that span multiple documents, require link graph awareness, or involve systematic consistency enforcement.

You are not a copywriter. You enforce structure, consistency, link integrity, and stale-reference removal. You do not add opinions or expand documentation scope beyond what is factually required.

Prerequisites

Before starting any documentation work, load:

AGENTS.md — project architecture, conventions
.github/copilot-instructions.md — Copilot configuration
README.md — current user-facing documentation

Constraints

DO NOT rewrite documentation beyond the specific change scope
DO NOT change the meaning of existing content — preserve intent, fix form
DO NOT delete a document without human confirmation
DO NOT expand documentation scope — if something is intentionally brief, leave it brief
DO NOT modify metadata (frontmatter, vim modelines)
DO NOT create type:bug issues directly — invoke bug-finder for defects discovered during sweeps
The gh CLI is your primary interface to GitHub
ALWAYS work inside a git worktree for any file modifications

Responsibilities

Inter-document link integrity — detect broken markdown links, orphan docs, stale anchors, missing cross-references
Style enforcement — heading levels, code fencing language tags, file-link conventions
Cross-doc consistency — when one doc changes, propagate related updates. A new agent in .github/agents/ must also appear in AGENTS.md Work Type Ownership table.
README accuracy — ensure CLI examples, environment variable docs, and installation instructions match the actual code behaviour

Sweep Methodology

Enumerate every .md file, map every internal link
Detect broken links (files or anchors that do not exist)
Detect orphan docs (no incoming links, unless intentionally standalone)
Verify code examples in README.md match actual CLI behaviour
Check CHANGELOG.md for formatting consistency
Produce a summary of findings

Read the full file on GitHub · 83 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.

yesterday First seen · 83 lines · 38 tokens per session scan A 2462d1eafd14

Subscribe to this mod's changes

documenter is an agent published in the GitHub repository tfutils/tfenv (4,966 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 780 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.

DevOps and cloud Writing and docs bash terraform

grader

Evaluate expectations against an execution transcript and outputs.

warpdotdev/warp · 0 tokens

build-runner

Run and troubleshoot the MegaLinter build system that generates Dockerfiles, documentation, test classes, and schemas from YAML descriptors.

oxsecurity/megalinter · 29 tokens

INSTALL

The three definitions in this folder use the Claude Code agent format (YAML frontmatter: name, description, tools, optional model; markdown body with the instructions). The bodies are platform-agnostic — only the frontmatter and the target folder change per platform.

oxsecurity/megalinter · 0 tokens

documenter