What is document-flows?

A document generator that reads integration flows from APIPASS and produces a corporate Word document, with an optional PDF version. The document explains connected systems, triggers, steps, and error handling.

Use it to document one project, a group of flows, or all flows by category, with optional sequence diagrams.

It removes the need to copy integration details into a technical document by hand. APIPASS is the source of the flow data, so no manual JSON upload is needed.

document-flows — Skill for Claude Code and Codex by APIPASS-Integrations: A document generator that reads integration flows from APIPASS…

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/apipass-integrations/apipass-headless/document-flows

Any agent

npx skills add APIPASS-Integrations/apipass-headless --skill document-flows

Clone the repo

git clone --depth 1 https://github.com/APIPASS-Integrations/apipass-headless

Made for: Claude Code, Codex.

Or install apipass-integrations, the plugin that ships this one along with the rest of its 13 skills, 2 agents, 1 hook, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/apipass-integrations/apipass-headless/document-flows.svg)](https://agentmods.dev/skills/apipass-integrations/apipass-headless/document-flows)

Your own site

<a href="https://agentmods.dev/skills/apipass-integrations/apipass-headless/document-flows"><img src="https://agentmods.dev/badge/skills/apipass-integrations/apipass-headless/document-flows.svg" alt="Measured on agentmods" height="20"></a>

Per session 91 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,861 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.00091	$0.03861
Opus 5	$0.00046	$0.01930
Sonnet 5	$0.00018	$0.00772
Haiku 4.5	$0.00009	$0.00386

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

Security

Grade A, and why

document-flows 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 4d 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.

plugins/apipass-integrations/skills/document-flows/SKILL.md · 308 lines

How it starts

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

Gerador de Documentacao de Integracoes — APIPASS

Produz um documento corporativo (.docx, com PDF opcional) descrevendo os fluxos de um projeto APIPASS. Os fluxos sao lidos direto da APIPASS via MCP — nao ha upload manual de JSON. A montagem do arquivo Word e delegada a skill anthropic-skills:docx.

Estrutura do entregavel (padrao do "doc SAP de referencia"):

CAPA            -> nome APIPASS, projeto/cliente, versao, data, sistemas integrados
1. Visao Geral  -> prosa + tabela indice (fluxo, acionamento, nº de steps)
2..N. Por fluxo -> descricao + informacoes tecnicas + tabela de etapas
Final. Tratamento de Erros e Resiliencia

1. Coletar inputs do usuario

Se faltarem, pergunte numa unica mensagem (use AskUserQuestion):

Projeto/cliente — para resolver o projectId via MCP (pode vir como argumento).
Nome para a capa e cabecalho — ex. "Mondelez", "JBS Terminais". Parametriza a capa; nunca use nome hardcoded de cliente anterior.
Organizacao — um documento por projeto / um consolidado / por categoria.
Incluir diagramas de sequencia? — sim / nao.

2. Coletar os fluxos via MCP

list_projects — resolva o projectId pelo nome informado. Se houver mais de um match, liste-os e confirme com o usuario antes de seguir.
list_flows(projectId) — lista os fluxos do projeto.
Para cada fluxo a documentar: export_flow_json(flowId) (exportacao completa) ou get_flow_development(flowId) (steps). Use o que retornar a estrutura mais completa.

Estrutura do specflow (steps, trigger, contadores) esta em /apipass-integrations:apipass-patterns. Anatomia do FlowStep e do mappingAttributes em /apipass-integrations:apipass-actions. Se uma tool pedir login, mostre a authorizeUrl ao usuario e refaca.

3. Filtrar rascunhos e legados

Ignore fluxos cujo nome contenha (case-insensitive): teste, aaaa, copy, old, exemplo, bkp, backup, rascunho. Antes de gerar, liste para o usuario o que foi incluido vs. ignorado e deixe-o ajustar.

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

4d ago First seen · 308 lines · 91 tokens per session scan A 074a16f4f730

Subscribe to this mod's changes

document-flows is a skill published in the GitHub repository APIPASS-Integrations/apipass-headless (2 stars, last pushed 25d ago), licensed Apache-2.0. It adds 91 tokens to every session and 3,861 once invoked, about $0.0005 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-31.

Documents PDF

pydicom

Use pydicom to read, inspect, write, transform, and safely preflight local DICOM datasets and pixel data. Applies to DICOM metadata, transfer syntaxes, compression plugins, frames, private elements, JSON, and bounded de-identification review.

K-Dense-AI/scientific-agent-skills · 56 tokens

foundry-hosted-agent-validation

Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.

microsoft/agent-framework · 82 tokens

document-flows