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/vpeetla-ai/react-agent-pattern/aegis-gatewaynpx skills add vpeetla-ai/react-agent-pattern --skill aegis-gatewaygit clone --depth 1 https://github.com/vpeetla-ai/react-agent-patternWrote 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/vpeetla-ai/react-agent-pattern/aegis-gateway)<a href="https://agentmods.dev/skills/vpeetla-ai/react-agent-pattern/aegis-gateway"><img src="https://agentmods.dev/badge/skills/vpeetla-ai/react-agent-pattern/aegis-gateway.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.00058 | $0.00311 |
| Opus 5 | $0.00029 | $0.00156 |
| Sonnet 5 | $0.00012 | $0.00062 |
| Haiku 4.5 | $0.00006 | $0.00031 |
Grade A, and why
aegis-gateway 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.
This is a copy
100% identical to aegis-gateway — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
AegisAI Gateway Integration
When required
Any side effect leaving the system:
- Publish to LinkedIn/X/Substack
- Send Slack/Telegram/WhatsApp messages
- Deploy or git push to protected branches (prefer PR workflow)
Pattern
# integrations/aegis_gateway.py (existing in VAP, AegisLoop, Content Factory)
result = await gateway.request_tool(
tool_name="notify_slack",
payload={...},
agent_id="...",
run_id="...",
)
if result.requires_hitl:
# pause until approval
Env vars
AEGISAI_API_BASE_URL=https://...
AEGISAI_API_KEY=...
Dev mode
- If gateway URL unset → fail open with logged warning (local dev only)
- Never fail open in production configs
Do not
- Embed policy logic in orchestrator prompts — policy lives in AegisAI/OPA
- Bypass gateway "temporarily" in production code paths
Reference
aegisai-enterprise-agent-platform — gateway SDK + POST /api/gateway/tool-request
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 · 53 lines · 58 tokens per session scan A 6f80d303827b
aegis-gateway is a skill published in the GitHub repository vpeetla-ai/react-agent-pattern (2 stars, last pushed today), licensed MIT. It adds 58 tokens to every session and 311 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to aegis-gateway, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
aegis-gateway
Integrate AegisAI gateway before tool side effects (notify, publish, deploy). Use when adding Slack/Telegram/WhatsApp notify, content publish, or any irreversible external action in VAP, AegisLoop, or ai-content-factory.
setup-vpeetla-skills
Bootstrap a vpeetla-ai repo for org skills: issue tracker, triage labels, docs paths, and CONTEXT.md placement. Use when onboarding a new repo, first clone, or when the user says setup skills or configure agent workflow.
langgraph-orchestration
Build or modify LangGraph StateGraph agents in vpeetla-ai repos: typed state, nodes, conditional edges, MemorySaver, interruptbefore HITL. Use when adding orchestrators, coding loops, or multi-agent graphs.
deploy-vercel-render
Deploy vpeetla-ai demos: Vercel static/Next.js frontends, Render FastAPI backends, env vars, free tier gotchas. Use when shipping demos, fixing deploy failures, or adding render.yaml / vercel.json.
hitl-side-effects
Add human-in-the-loop gates for irreversible actions: LangGraph interruptbefore, AegisAI approval queue, UI approve/resume endpoints. Use when shipping, publishing, notifying, or merging agent-generated changes.
portfolio-adr
Write ADRs, case studies, and portfolio copy for ai-architecture-portfolio and venkat-ai-portfolio. Use when documenting decisions, updating ecosystem pages, or syncing GitHub profile README with live demos.