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 agentmods add agents/tfutils/tfscaffold/documentergit clone --depth 1 https://github.com/tfutils/tfscaffoldWhat 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.00598 |
| Opus 5 | $0.00019 | $0.00299 |
| Sonnet 5 | $0.00008 | $0.00120 |
| Haiku 4.5 | $0.00004 | $0.00060 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 60 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 tfscaffold 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 configurationREADME.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:bugissues directly — invokebug-finderfor defects discovered during sweeps - The
ghCLI 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 inAGENTS.mdWork Type Ownership table. - README accuracy — ensure CLI examples, environment variable docs, and usage instructions match the actual code behaviour
Sweep Methodology
- Enumerate every
.mdfile, 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
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 · 60 lines · 38 tokens per session scan A 08448832d658
documenter is an agent published in the GitHub repository tfutils/tfscaffold (281 stars, last pushed 4mo ago), licensed MIT. It adds 38 tokens to every session and 598 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.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.