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 instructions/roxyapi/astrology-ai-chatbot/agents-mdgit clone --depth 1 https://github.com/RoxyAPI/astrology-ai-chatbotWhat 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.01369 | $0.01369 |
| Opus 5 | $0.00685 | $0.00685 |
| Sonnet 5 | $0.00274 | $0.00274 |
| Haiku 4.5 | $0.00137 | $0.00137 |
Grade A, and why
astrology-ai-chatbot AGENTS.md 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 2d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agents Guide
This is an MIT licensed RoxyAPI template: a white label AI astrology chatbot built with Next.js 16 and the Vercel AI SDK, made to be cloned, customised, rebranded, and resold as your own product. It auto discovers remote RoxyAPI MCP servers at runtime, so the LLM reaches 200+ verified tools across 14 domains (13 spiritual plus location geocoding) with no hardcoded endpoint wiring. You are most likely a coding agent helping someone build their own product on top of this template. More templates to fork: https://roxyapi.com/starters
Canonical RoxyAPI references (use these, do not guess)
Prefer these live sources over memory for any RoxyAPI path, field, SDK method, or limit. They are always current.
- Docs MCP (no API key): connect
https://roxyapi.com/mcp/docs(Streamable HTTP, one toolsearch_docs). Ask it for any endpoint, field, auth detail, or integration step instead of hardcoding a path.{ "mcpServers": { "roxy-docs": { "type": "http", "url": "https://roxyapi.com/mcp/docs" } } } - Agent playbook:
https://roxyapi.com/AGENTS.md, implementation rules for building on RoxyAPI. - Discovery context:
https://roxyapi.com/llms.txt(concise) andhttps://roxyapi.com/llms-full.txt(deep). - Live OpenAPI spec:
https://roxyapi.com/api/v2/openapi.json, the source of truth for every field and example. Never invent a response field. - Live playground:
https://roxyapi.com/api-reference. Sitemap:https://roxyapi.com/sitemap.txt.
Setup
- Get an API key at https://roxyapi.com/pricing
- Copy
.env.exampleto.env.localand set:ROXYAPI_KEYfor RoxyAPI access- One LLM provider key:
GOOGLE_GENERATIVE_AI_API_KEY(default),ANTHROPIC_API_KEY, orOPENAI_API_KEY - Optional
LLM_PROVIDER:gemini,anthropic, oropenai - Optional
ROXYAPI_PRODUCTSto limit which MCP servers connect, e.g.astrology,tarot,location
npm install, thennpm run dev, then open http://localhost:3000npm testruns the vitest suite (env resolution, product resolution, system-prompt contract)
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.
- 2d ago First seen · 60 lines · 1,369 tokens per session scan A dd69ad1cc159
astrology-ai-chatbot AGENTS.md is an instructions file published in the GitHub repository RoxyAPI/astrology-ai-chatbot (8 stars, last pushed 6d ago), licensed MIT. It adds 1,369 tokens to every session, about $0.0068 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 instructions, from other repositories
astral-mcp AGENTS.md
AGENTS.md instructions for davidmosiah/astral-mcp, covering agent development notes, scope, layout, commands and rules.
gptme AGENTS.md
AGENTS.md instructions for gptme/gptme, covering agent instructions for gptme, git workflow, code style, testing and project structure.
AstrBot copilot-instructions.md
Copilot instructions for AstrBotDevs/AstrBot, covering astrbot development instructions, working effectively, bootstrap and install dependencies, running the application and dashboard build (vue.js/node.js).
Codex-Skills AGENTS.md
Instructions for TheGoat395/Codex-Skills, covering repository operating notes, required checks, evidence rules and change hygiene.
souls-directory CLAUDE.md
Instructions for thedaviddias/souls-directory, covering claude.md — project context for ai assistants, project overview, tech stack, critical rules and database is convex.
nextarter-tailwind AGENTS.md
AGENTS.md instructions for agustinusnathaniel/nextarter-tailwind, covering next.js: always read docs before coding, ai agent guidance: nextarter-tailwind, 1. mental model for agents, implementation delegation and tooling strategy.