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/impactbrussels/ainativeos/gateway-agent-opsnpx skills add impactbrussels/AINativeOS --skill gateway-agent-opsgit clone --depth 1 https://github.com/impactbrussels/AINativeOSWrote 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/impactbrussels/ainativeos/gateway-agent-ops)<a href="https://agentmods.dev/skills/impactbrussels/ainativeos/gateway-agent-ops"><img src="https://agentmods.dev/badge/skills/impactbrussels/ainativeos/gateway-agent-ops.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.1 | $0.00146 | $0.01490 |
| Opus 5 | $0.00073 | $0.00745 |
| Sonnet 5 | $0.00029 | $0.00298 |
| Haiku 4.5 | $0.00015 | $0.00149 |
Grade A, and why
gateway-agent-ops 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 5d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gateway Agent Ops
One big assistant for operations is the trap that wears a different coat. For a week it is magic, then it routes a refund through the marketing logic, books a board call for 3am, and burns tokens all weekend reconciling two records that cannot be reconciled. Monday brings a four-figure bill and a system nobody trusts. The fix is not a better mega-prompt. It is a thin switchboard in front of a roster of narrow specialists, each one watched, capped, and easy to fix when it misbehaves.
The method
Build the switchboard, not the hero. Full framework: references/gateway-design.md. Source: Handbook Chapter 13.
Step 1: List the request classes
Write down every kind of request the inbox actually receives, then collapse them to the smallest set a narrow specialist could own. One class, one job.
| Request class | One-job specialist | Small toolset |
|---|---|---|
| Summarise this thread | Summariser | read-only |
| Draft this grant section | Grant-drafter | retrieval + template |
| Check this against the rulebook | Compliance-checker | rulebook lookup |
| Find a slot and book it | Scheduler | calendar write |
Step 2: Design the classification schema
The gateway reads the request and emits one structured verdict: {class, specialist, confidence, reason}. It does one job, route, and gets out of the way. The moment it carries domain logic you have rebuilt the God Agent with an innocent name.
Step 3: Set the route / escalate / refuse rule
For each verdict, decide the disposition before going live.
| Situation | Disposition |
|---|---|
| Confident match to a specialist | Route |
| Low confidence, or no specialist fits | Escalate to a human |
| Irreversible action (filing, payment, send) | Route to draft, human signs |
| Out of scope or unsafe | Refuse, log, surface |
Step 4: Wrap every specialist in guardrails
No specialist ships without all four. These are the seatbelt, not the polish.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 99 lines · 146 tokens per session scan A 15f05bc10ea5
gateway-agent-ops is a skill published in the GitHub repository impactbrussels/AINativeOS (1 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 146 tokens to every session and 1,490 once invoked, about $0.0007 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
remember
Review reusable project knowledge and decide what belongs in project memory, notepad, or durable docs.
agent-session-monitor
Real-time agent conversation monitoring - monitors Higress access logs, aggregates conversations by session, tracks token usage. Supports web interface for viewing complete conversation history and costs. Use when users ask about current session token consumption, conversation history, or cost statistics.
docx-comment-reply
Reply to comments (批注) in Word .docx/.doc files: extract comment context, draft replies, write threaded replies back, and validate OOXML.
explaining-machine-learning-models
Explain trained machine learning models through feature attribution, local explanations, and behavior summaries. Use as an explicit/manual helper once a model already exists, not for training ownership, leakage auditing, or general ML strategy selection.
nw-ddd-eventsourcing
Event Sourcing and CQRS as DDD implementation patterns — when to use, aggregate event streams, projections, snapshots, sagas, upcasting, conflict resolution.
nw-leanux-methodology
LeanUX backlog management methodology - user story template, story sizing, story states, task types, Definition of Ready/Done, anti-pattern detection and remediation.