astrology-ai-chatbot AGENTS.md

A set of instructions for building an AI astrology chatbot from a customizable Next.js template. The template connects to RoxyAPI, which provides astrology-related tools and location lookup, and requires location details before creating charts.

In plain words
What is it for?
Customizing, rebranding, and reselling the chatbot template, connecting its runtime-discovered tools, and implementing location and astrology-chart features using RoxyAPI guidance.
Why use it?
It gives coding agents the project’s setup, data flow, and authoritative documentation sources so they do not guess API paths or integration details.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/roxyapi/astrology-ai-chatbot/agents-md
Clone the repo
git clone --depth 1 https://github.com/RoxyAPI/astrology-ai-chatbot

Made for: Codex, OpenCode.

Per session 1,369 This file is loaded in full into every session.
When invoked 1,369 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 2d ago against content hash dd69ad1cc159, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

AGENTS.md · 60 lines

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 tool search_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) and https://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.example to .env.local and set:
    • ROXYAPI_KEY for RoxyAPI access
    • One LLM provider key: GOOGLE_GENERATIVE_AI_API_KEY (default), ANTHROPIC_API_KEY, or OPENAI_API_KEY
    • Optional LLM_PROVIDER: gemini, anthropic, or openai
    • Optional ROXYAPI_PRODUCTS to limit which MCP servers connect, e.g. astrology,tarot,location
  • npm install, then npm run dev, then open http://localhost:3000
  • npm test runs the vitest suite (env resolution, product resolution, system-prompt contract)

Read the full file on GitHub · 60 lines

Changes

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.

  1. 2d ago First seen · 60 lines · 1,369 tokens per session scan A dd69ad1cc159

Subscribe to this mod's changes

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.