Borrowing it
Nothing to install: this file belongs to skygazer42/pokemon-chat. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/skygazer42/pokemon-chat/develop/AGENTS.mdgit clone --depth 1 https://github.com/skygazer42/pokemon-chatWrote 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/instructions/skygazer42/pokemon-chat/agents-md)<a href="https://agentmods.dev/instructions/skygazer42/pokemon-chat/agents-md"><img src="https://agentmods.dev/badge/instructions/skygazer42/pokemon-chat/agents-md.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.00739 | $0.00739 |
| Opus 5 | $0.00369 | $0.00369 |
| Sonnet 5 | $0.00148 | $0.00148 |
| Haiku 4.5 | $0.00074 | $0.00074 |
Grade A, and why
pokemon-chat 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 6d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This repository contains a FastAPI backend (server/, src/) and a Vue3 frontend (web/), plus Docker Compose infra (docker/).
Quick Commands
- Backend lint:
python -m ruff check server src scripts - Backend format check:
python -m ruff format --check server src scripts - Backend tests:
python -m pytest - All checks (CI-like):
make check(runs backend + frontend checks) - Docker (from repo root):
- App only (api + web):
make docker-up - App + infra (neo4j/milvus/mysql/...):
make docker-up-infra - Full (app + infra + mcp):
make docker-up-full
- App only (api + web):
Repo Layout
server/: FastAPI app + routerssrc/: core logic (agents, retrieval, graph, stores, utils)web/: Vue3 frontend (Vite)docker/: dockerfiles +docker-compose.yml+ nginx configscripts/: bootstrap/doctor/import helpersresources/: data/models/cache (often mounted into containers; large assets may be excluded from Docker build context)
Skills
A "skill" is a set of local instructions stored in a SKILL.md file. Available skills in this session:
skill-creator: Create/update skills that extend Codex with specialized knowledge/workflows/tooling.- File:
C:/Users/luke/.codex/skills/.system/skill-creator/SKILL.md
- File:
skill-installer: Install Codex skills into$CODEX_HOME/skillsfrom a curated list or a GitHub repo path.- File:
C:/Users/luke/.codex/skills/.system/skill-installer/SKILL.md
- File:
When to Use a Skill (Trigger Rules)
- If the user names a skill (either
$SkillNameor plain text), OR the task clearly matches a skill description above, use that skill for that turn. - Multiple skill mentions mean use all of them.
- Do not carry skills across turns unless the user re-mentions them.
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.
- 6d ago First seen · 62 lines · 739 tokens per session scan A d1eb316a027d
pokemon-chat AGENTS.md is an instructions file published in the GitHub repository skygazer42/pokemon-chat (406 stars, last pushed 7mo ago), licensed MIT. It adds 739 tokens to every session, about $0.0037 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-30.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.