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.
git clone --depth 1 https://github.com/luanpdd/kit-mcpWrote 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/commands/luanpdd/kit-mcp/auditar-toil)<a href="https://agentmods.dev/commands/luanpdd/kit-mcp/auditar-toil"><img src="https://agentmods.dev/badge/commands/luanpdd/kit-mcp/auditar-toil/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/commands/luanpdd/kit-mcp/auditar-toil"><img src="https://agentmods.dev/badge/commands/luanpdd/kit-mcp/auditar-toil.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.00048 | $0.01603 |
| Opus 5.5 | $0.00019 | $0.00641 |
| Sonnet 5.5 | $0.00010 | $0.00321 |
| Haiku 4.5 | $0.00005 | $0.00160 |
Grade A, and why
auditar-toil 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 1mo 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cria/Atualiza:
.planning/TOIL-AUDIT.md— lista priorizada P0/P1/P2 com 6 critérios scored + esforço de automação estimado
Após: o user tem audit acionável para reduzir toil pelo time. Phase 39 INT-OBS-02 integra ao omm-auditor (v1.9) — Capacidade 3 do OMM scoring usa este audit.
Flags:
--time-window <Nm|Nd>— janela de git history a analisar (default:3m= 3 meses)--team-size <N>— número de pessoas no time (default: inferido viagit shortlog -sn)--output <path>— caminho do output (default:.planning/TOIL-AUDIT.md)--runbooks-paths <p1,p2,...>— paths customizados de runbooks (default:runbooks/, docs/runbooks/, ops/, scripts/, .github/workflows/)
Exemplos:
/auditar-toil # defaults — 3m de git, team auto-detect
/auditar-toil --time-window 6m --team-size 5 # janela maior + team explícito
/auditar-toil --output .planning/audit/toil-2026-Q2.md # path customizado
Pré-requisito: repositório git inicializado (sem isso, agent skip git log analysis e usa apenas scripts/runbooks).
1. Parsear argumentos
TIME_WINDOW=$(echo "$ARGUMENTS" | grep -oE -- '--time-window [^ ]+' | awk '{print $2}')
TEAM_SIZE=$(echo "$ARGUMENTS" | grep -oE -- '--team-size [^ ]+' | awk '{print $2}')
OUTPUT_PATH=$(echo "$ARGUMENTS" | grep -oE -- '--output [^ ]+' | awk '{print $2}')
RUNBOOKS=$(echo "$ARGUMENTS" | grep -oE -- '--runbooks-paths [^ ]+' | awk '{print $2}')
[ -z "$TIME_WINDOW" ] && TIME_WINDOW="3m"
[ -z "$OUTPUT_PATH" ] && OUTPUT_PATH=".planning/TOIL-AUDIT.md"
# PT-BR: criar destination dir
mkdir -p "$(dirname "$OUTPUT_PATH")"
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.
- 1mo ago First seen · 130 lines · 48 tokens per session scan A ee4c80ad8f01
auditar-toil is a command published in the GitHub repository luanpdd/kit-mcp (4 stars, last pushed yesterday), licensed MIT. It adds 48 tokens to every session and 1,603 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.