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 agents/grtsnx/payba3/payba3git clone --depth 1 https://github.com/grtsnx/payba3Wrote 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/agents/grtsnx/payba3/payba3)<a href="https://agentmods.dev/agents/grtsnx/payba3/payba3"><img src="https://agentmods.dev/badge/agents/grtsnx/payba3/payba3.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.00000 | $0.01056 |
| Opus 5 | $0.00000 | $0.00528 |
| Sonnet 5 | $0.00000 | $0.00211 |
| Haiku 4.5 | $0.00000 | $0.00106 |
Grade A, and why
payba3 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
payba3 Agent Integration Guide
This file is the agent-facing contract for using @grtsnx/payba3 inside IDE assistants, AI coding agents, workflow builders, and tool servers.
Discovery Order
When an agent needs to integrate payba3:
- Read
@grtsnx/payba3/llms.txt. - Read
@grtsnx/payba3/agents.md. - Read
@grtsnx/payba3/llms-full.txtwhen broader context is needed. - Read every provider-specific file needed for the requested channel:
@grtsnx/payba3/llms/paystack.txt@grtsnx/payba3/llms/safehaven.txt@grtsnx/payba3/llms/seerbit.txt@grtsnx/payba3/llms/opay.txt@grtsnx/payba3/llms/mono.txt@grtsnx/payba3/llms/monnify.txt@grtsnx/payba3/llms/qoreid.txt
Core Contract
- Package:
@grtsnx/payba3 - Runtime: server-side JavaScript or TypeScript
- Main import:
createPayba3 - Provider selector:
payba3.use('<provider>') - Error surface:
Payba3Error - Supported providers:
paystack,safehaven,seerbit,opay,mono,monnify,qoreid
import { createPayba3 } from '@grtsnx/payba3';
const payba3 = createPayba3({
paystack: {
secretKey: process.env.PAYSTACK_SECRET_KEY,
},
});
const paystack = payba3.use('paystack');
IDE Agent Instructions
When generating code:
- Install
@grtsnx/payba3if it is missing. - Generate server-side code only.
- Ask the developer for the provider they want to use.
- Ask only for the credentials required by that provider.
- Prefer environment variables or the host app's secret manager.
- Use explicit
createPayba3({ provider: { ...config } })configuration when it improves clarity. - Keep provider-specific request validation in the host app or tool wrapper.
- Never place provider secrets in frontend code, generated examples, comments, tests, logs, or fixtures.
Tool Wrapper Pattern
Agents should expose narrow tools that match business actions, not raw provider clients.
import { createPayba3 } from '@grtsnx/payba3';
const payba3 = createPayba3({
paystack: {
secretKey: process.env.PAYSTACK_SECRET_KEY,
},
});
type InitializeCheckoutInput = {
email: string;
amountInKobo: number;
reference: string;
};
export async function initializePaystackCheckout(
input: InitializeCheckoutInput,
) {
return payba3.use('paystack').initializeOneTimeCheckout({
email: input.email,
amountInKobo: input.amountInKobo,
currency: 'NGN',
reference: input.reference,
});
}
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 · 127 lines · 0 tokens per session scan A e69dd65d14f4
payba3 is an agent published in the GitHub repository grtsnx/payba3 (2 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,056 tokens. 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 agents, from other repositories
mp-integration-expert
Use when implementing, reviewing, or debugging any Mercado Pago payment integration. Routes requests to one of four skills, supports offline scaffolding and local checks, and connects to MCP only immediately before a selected live tool.
alphacouncil-news_industry_management
News & Industry Analyst for AlphaCouncil equity research. news, industry, management.
alphacouncil-insider_sec
Insider & SEC Filings Analyst for AlphaCouncil equity research. sec, form-4, filings, buyback.
alphacouncil-social_pulse
Retail Sentiment and Crowding Analyst for AlphaCouncil equity research. sentiment, crowding, social.
alphacouncil-earnings_deep_dive
Earnings Deep Dive Analyst for AlphaCouncil equity research. earnings, margins, segments, cash-flow.
alphacouncil-market_narrative
Market Narrative Analyst for AlphaCouncil equity research. narrative, positioning, macro-context.