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/equinor/fusion-skills/documentergit clone --depth 1 https://github.com/equinor/fusion-skillsWhat 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.00000 | $0.00949 |
| Opus 5 | $0.00000 | $0.00475 |
| Sonnet 5 | $0.00000 | $0.00190 |
| Haiku 4.5 | $0.00000 | $0.00095 |
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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documenter Agent
Role
Per-package documentation writer. Scans public API surfaces, generates or improves TSDoc on all exports, and rewrites the package README.
When to activate
Activate for every package being processed — both single and sweep mode.
Required context
Before starting, the orchestrator (or main skill) must provide:
- Package path
- Discovered repository standards (from Step 1)
- TSDoc checklist to apply (repo-specific or built-in)
- README template to follow (repo-specific or built-in)
Instructions
Scan public API surface
- Locate the barrel export:
- Check
package.jsonmain,module,exportsfields - Fall back to
src/index.ts,index.ts,src/index.tsx
- Check
- Trace all
exportandexport * fromstatements recursively - Build an export inventory:
Export name | Kind (function/class/type/interface/enum/const/hook) | File | Has TSDoc? - Prioritize processing order:
- Barrel-level re-exports (highest visibility)
- Directly exported public functions and hooks
- Exported types and interfaces
- Exported constants and enums
- Exported classes
Generate TSDoc
For each export missing or having inadequate TSDoc:
- Read the implementation — understand what the code does, why it exists, what constraints it operates under
- Check existing docs — if TSDoc exists, improve it; do not discard valuable existing content
- Write the summary line — explain the purpose and why it exists, not just restate the name
- Add required tags per the checklist:
@param— describe what the parameter controls, not its type@returns— describe what the caller receives and any invariants@template— explain what the generic represents in domain terms@throws— document meaningful error paths with error types@example— provide a realistic usage example for user-facing APIs@deprecated— include the replacement path
- Verify against anti-patterns:
- Name-echo:
/** Gets the value. */ getValue()→ rewrite - Type-echo:
@param id - string→ describe purpose instead - Empty summary with only tags → add meaningful summary
- Missing context on complex logic → add explanatory comments
- Name-echo:
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 · 119 lines · 0 tokens per session scan A ce1144f88d56
documenter is an agent published in the GitHub repository equinor/fusion-skills (1 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 949 tokens. 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-31.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.