fetch_documentation

A command for fetching online documentation and saving a project-focused summary in the ai_docs directory.

In plain words
What is it for?
Use it to collect implementation examples, actionable guidance, and phase or component tags from documentation for later project work.
Why use it?
It turns a documentation URL into notes that are checked against the project's specifications and existing documentation, reducing duplicated or disconnected research.

Command for Claude Code

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 commands/consiliency/flutter-structurizr/fetch_documentation
Clone the repo
git clone --depth 1 https://github.com/Consiliency/Flutter-Structurizr

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 239 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.00000 $0.00239
Opus 5 $0.00000 $0.00120
Sonnet 5 $0.00000 $0.00048
Haiku 4.5 $0.00000 $0.00024

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

Security

Grade A, and why

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

.claude/commands/fetch_documentation.md · 27 lines

What it actually says

Fetch Documentation

Description

Use the WebFetch TOOL to read the documentation at $ARGUMENTS.

Process

  1. Read the documents in the ../specs directory to understand the project goals
  2. Fetch documentation from the specified URL
  3. Cross-reference fetched documentation with existing specs and ../ai_docs to avoid redundancy
  4. CREATE a new file that captures the content in the ../ai_docs directory
    1. At the top of the new file, extract and summarize actionable insights or implementation examples
    2. Tag the documentation with relevant phase/component for easier future retrieval
    3. Make sure to capture all information that may be useful for the project goals.
    4. Make sure to keep specific implementation examples
  5. Name the file with a name that makes sense
  6. If there is a similar file already in the ../ai_docs directory, use the same name with a new version number

Usage

/project:fetch_documentation <url>

Examples

/project:fetch_documentation https://structurizr.com/help
/project:fetch_documentation https://c4model.com/
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 · 27 lines · 0 tokens per session scan A bc86e4accc6d

Subscribe to this mod's changes

fetch_documentation is a command published in the GitHub repository Consiliency/Flutter-Structurizr (7 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 239 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.