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 skills add APIPASS-Integrations/apipass-headless --skill apipass-usagegit 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/apipass-usage)<a href="https://agentmods.dev/skills/apipass-integrations/apipass-headless/apipass-usage"><img src="https://agentmods.dev/badge/skills/apipass-integrations/apipass-headless/apipass-usage/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/apipass-integrations/apipass-headless/apipass-usage"><img src="https://agentmods.dev/badge/skills/apipass-integrations/apipass-headless/apipass-usage.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00086 | $0.00899 |
| Opus 5 | $0.00043 | $0.00449 |
| Sonnet 5 | $0.00017 | $0.00180 |
| Haiku 4.5 | $0.00009 | $0.00090 |
Grade A, and why
apipass-usage 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 8d 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Consumo e uso na APIPASS
Regra de roteamento (importante)
Perguntas de contagem/listagem agregada (quantos fluxos, quais fluxos, quantas execucoes) usam os SUMARIOS, NUNCA execution-logs:
| Pergunta | Ferramenta |
|---|---|
| "quantos fluxos executaram no periodo" / "quais fluxos rodaram" | get_execution_summary(period: "flow", startDate, endDate, timezone) — retorna um item por fluxo com a contagem |
| "quantas execucoes por dia/hora/mes" | get_execution_summary(period: "daily"|"hourly"|"monthly", ...) |
| "quantas execucoes no total" / "uso da conta" / "uso do flow engine" | get_usage_summary(metric: "total"|"average"|"flow-engine-usage") |
Os execution-logs (list_flow_execution_logs, get_flow_execution_log, etc.) sao para inspecionar/depurar execucoes especificas — NAO para contar ou listar quais fluxos rodaram. Listar logs e paginado e pesado; para volume/quais-fluxos, o sumario ja vem agregado.
Duas ferramentas cobrem consumo, com formatos diferentes — escolha pela pergunta:
1. Serie temporal: get_execution_summary
Consumo ao longo do tempo (para tendencias/graficos). Obrigatorios: period, startDate, endDate, timezone.
period:daily|hourly|monthly|flow(agrupa por fluxo no periodo).- Filtros opcionais:
projectId,flowId,environmentId. - Ordenacao opcional:
order,sortBy.
Use para: "consumo por dia do ultimo mes", "execucoes por hora ontem", "consumo mensal do ano", "consumo por fluxo no projeto X".
2. Agregado da conta: get_usage_summary
Numeros consolidados da conta (para "quanto consumi" / cobranca / quota). Todos os params sao opcionais — sem startDate/endDate retorna o consumo corrente/total.
metric:total(total de requisicoes/execucoes) |average(media) |flow-engine-usage(uso do flow-engine — relevante para cobranca/limites).- Opcionais:
startDate,endDate,accountId,timezone.
Use para: "quanto consumi este mes", "uso total da conta", "uso do flow engine", "media de execucoes".
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.
- 8d ago First seen · 47 lines · 86 tokens per session scan A 2fa8a14cd5f8
apipass-usage is a skill published in the GitHub repository APIPASS-Integrations/apipass-headless (2 stars, last pushed 29d ago), licensed Apache-2.0. It adds 86 tokens to every session and 899 once invoked, about $0.0004 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…