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/Hainrixz/agente-pagokitWrote 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/hainrixz/agente-pagokit/doctor)<a href="https://agentmods.dev/commands/hainrixz/agente-pagokit/doctor"><img src="https://agentmods.dev/badge/commands/hainrixz/agente-pagokit/doctor/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/hainrixz/agente-pagokit/doctor"><img src="https://agentmods.dev/badge/commands/hainrixz/agente-pagokit/doctor.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.00036 | $0.00475 |
| Opus 5 | $0.00018 | $0.00237 |
| Sonnet 5 | $0.00007 | $0.00095 |
| Haiku 4.5 | $0.00004 | $0.00047 |
Grade A, and why
doctor 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 11d 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.
What it actually says
You are entering the PagoKit doctor flow. Read-only audit — never write files.
-
Invoke the
doctorskill, which:- Reads
PAGOKIT_INTEGRATION.mdfrom the project root for context (provider, files generated, events routed, ORM, deploy target). - If the file is missing, asks the user which provider they're using and proceeds best-effort.
- Runs each check in the categories defined in the skill: Environment hygiene · Required env vars · Webhook handler quality · Idempotency · DB schema · Production-readiness pointer.
- Emits a per-check status line
[OK] / [WARN] / [FAIL]. - Produces a summary count and a "Next steps" list.
- Reads
-
Report the audit result to the user verbatim in their language. Format:
PagoKit Doctor — <provider> integration audit Generated <last_generated_at> · stack: <stack> · deploy: <deploy_target> Environment hygiene [OK] .gitignore covers .env [OK] .env not tracked in git ... Webhook handler [OK] app/api/webhook/stripe/route.ts verifies signature [FAIL] customer.subscription.updated not routed ... (per category) Summary: 17 OK · 2 warnings · 1 failure Next steps: 1. Route the missing event customer.subscription.updated (see templates/stripe/subscription.md). 2. Address the warnings before going live. -
Never echo secret values even when you read
.env. Just report match / no-match against pattern.
Anti-patterns
- Do NOT write files, run migrations, or modify settings during a
doctorflow. Pure read. - Do NOT recommend fixes that require live keys. First step is always: make the sandbox green.
- Do NOT skip categories. Even if early categories fail badly, run the full audit so the user gets a complete picture.
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.
- 11d ago First seen · 47 lines · 36 tokens per session scan A 5d0e8bfbfd1d
doctor is a command published in the GitHub repository Hainrixz/agente-pagokit (49 stars, last pushed 11d ago), licensed MIT. It adds 36 tokens to every session and 475 once invoked, about $0.0002 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-30.
Other commands, from other repositories
close-review
Month-end close / GL compliance check — invokes accounting-reviewer to produce TM-accounting-{slug}.md with double-entry integrity, ASC 606 revenue-recognition, period-lock, and SOX ITGC gaps.
procurement-review
Procurement / source-to-pay compliance check — invokes procurement-reviewer to produce TM-procurement-{slug}.md with three-way match, segregation-of-duties, OFAC-screening, and SOX procurement-controls gaps.
tax-review
Tax-filing compliance check — invokes tax-reviewer to produce TM-tax-{slug}.md with MeF e-file schema, Form 8879, PTIN/Circular 230, and IRC §7216 consent gaps.
merit-customers
Find or create a Merit Aktiva customer (or vendor).
merit-invoices
List, find, or inspect Merit Aktiva sales/purchase invoices.
search-flights
Search award flight availability across airlines.