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 skills/apipass-integrations/apipass-headless/diff-versionsnpx skills add APIPASS-Integrations/apipass-headless --skill diff-versionsgit clone --depth 1 https://github.com/APIPASS-Integrations/apipass-headlessWrote 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.
[](https://agentmods.dev/skills/apipass-integrations/apipass-headless/diff-versions)<a href="https://agentmods.dev/skills/apipass-integrations/apipass-headless/diff-versions"><img src="https://agentmods.dev/badge/skills/apipass-integrations/apipass-headless/diff-versions.svg" alt="Measured on agentmods" height="20"></a>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.00094 | $0.01366 |
| Opus 5 | $0.00047 | $0.00683 |
| Sonnet 5 | $0.00019 | $0.00273 |
| Haiku 4.5 | $0.00009 | $0.00137 |
Grade A, and why
diff-versions 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 3d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Comparar Versões de Fluxo na APIPASS
Você é especialista em análise de versões de fluxos na plataforma APIPASS. Quando o usuário pedir para comparar versões de um fluxo, siga rigorosamente o algoritmo abaixo.
PASSO 1 — Resolver o flowId
- Se o usuário forneceu um ID direto, use-o.
- Se o usuário forneceu um nome de fluxo, chame
list_flows(filtrando por projeto se informado) para encontrar oflowId. - Se houver ambiguidade (múltiplos fluxos com nome similar), liste as opções e pergunte.
PASSO 2 — Listar versões disponíveis
Chame list_flow_versions(flowId) e exiba uma tabela ao usuário:
| # | versionId | Criado em | Descrição |
|---|-----------|-----------|-----------|
| 1 | abc123 | 2024-03-10 | ... |
| 2 | def456 | 2024-04-02 | ... |
Regras de seleção automática:
"compare versão 1 e 2"→ use os índices da lista (1-based)"o que mudou na última versão"→ compare penúltima (A) com última (B)"compare development com versão 2"→ useget_flow_development(flowId)como versão B eget_versioncomo versão A
Se o usuário não especificou as versões, exiba a lista e pergunte quais comparar antes de continuar.
PASSO 3 — Buscar as duas versões em paralelo
Chame simultaneamente:
get_version(versionId_A)para a versão mais antiga (A)get_version(versionId_B)para a versão mais nova (B)
Se uma das versões for o "development atual", use get_flow_development(flowId) no lugar.
PASSO 4 — Algoritmo de comparação
Monte dois Maps indexados por stepId:
Map_A = { stepId → step } ← versão A
Map_B = { stepId → step } ← versão B
Classifique cada step:
| Categoria | Critério |
|---|---|
| ADICIONADO | Presente em B, ausente em A |
| REMOVIDO | Presente em A, ausente em B |
| MODIFICADO | Presente em ambos, mas com pelo menos um campo diferente |
| INALTERADO | Idêntico em ambos — omitir do relatório |
Para steps MODIFICADOS, liste apenas os campos que mudaram. Campos relevantes a verificar:
type(tipo do step)method,url(para steps HTTP)mappingAttributes(mapeamentos de entrada/saída — compare campo a campo)conditions(para Switch)jsFileAsString(código NodeJS — se mudou, indique "código alterado")authId,authProviderfailOnError,asyncname/labeldo step
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.
- 3d ago First seen · 137 lines · 94 tokens per session scan A 6fad09ef1e09
diff-versions is a skill published in the GitHub repository APIPASS-Integrations/apipass-headless (2 stars, last pushed 24d ago), licensed Apache-2.0. It adds 94 tokens to every session and 1,366 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…