PlayGodot: Instructions file for Codex

AGENTS.md

PlayGodot AGENTS.md is an instructions file for Codex, OpenCode from Randroids-Dojo/PlayGodot. It costs 685 tokens per session, scanned A, original, MIT.

A set of instructions for coding agents working on PlayGodot, a framework for testing Godot Engine games. It documents the project structure, prerequisites, tests, and release steps.

In plain words
What is it for?
It helps maintain the Python package and communication protocol, check tests, update versions, create Git tags, and publish GitHub releases.
Why use it?
It gives an agent the repository-specific context needed to make changes and prepare releases correctly.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is Randroids-Dojo/PlayGodot's own configuration. It tells Codex and OpenCode how to work on PlayGodot itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything PlayGodot configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Randroids-Dojo/PlayGodot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Randroids-Dojo/PlayGodot/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/Randroids-Dojo/PlayGodot

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for PlayGodot AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/randroids-dojo/playgodot/agents-md.svg)](https://agentmods.dev/instructions/randroids-dojo/playgodot/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/randroids-dojo/playgodot/agents-md"><img src="https://agentmods.dev/badge/instructions/randroids-dojo/playgodot/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 685 This file is loaded in full into every session.
When invoked 685 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00685 $0.00685
Opus 5 $0.00342 $0.00342
Sonnet 5 $0.00137 $0.00137
Haiku 4.5 $0.00068 $0.00068

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

Security

Grade A, and why

PlayGodot 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 · 91 lines

How it starts

The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent Instructions for PlayGodot

This file contains instructions for AI coding agents working on this repository.

Project Overview

PlayGodot is an external automation and testing framework for Godot Engine games. It uses Godot's native RemoteDebugger protocol via a custom Godot fork for communication. It consists of:

  • Python package (python/): The main testing library published to PyPI
  • Protocol (protocol/): JSON-RPC message definitions

Release Process

Prerequisites

  • Ensure all changes are merged to main
  • Verify tests pass

Steps to Release

  1. Update version in python/pyproject.toml:

    version = "X.Y.Z"
    
  2. Commit and push the version bump:

    git add python/pyproject.toml
    git commit -m "Bump version to X.Y.Z"
    git push origin main
    
  3. Create and push a git tag:

    git tag -a vX.Y.Z -m "Release vX.Y.Z - Brief description"
    git push origin vX.Y.Z
    
  4. Create a GitHub Release:

  5. PyPI publishing is automatic:

Manual PyPI Publishing (if needed)

If you need to publish manually or to TestPyPI:

  1. Build the package:

    cd python
    pip install build
    python -m build
    
  2. Upload to TestPyPI (for testing):

    pip install twine
    twine upload --repository testpypi dist/*
    
  3. Upload to PyPI:

    twine upload dist/*
    

Note: Manual uploads require a PyPI API token configured in ~/.pypirc or passed via -u __token__ -p <token>.

Read the full file on GitHub · 91 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 · 91 lines · 685 tokens per session scan A f8f659168049

Subscribe to this mod's changes

PlayGodot AGENTS.md is an instructions file published in the GitHub repository Randroids-Dojo/PlayGodot (38 stars, last pushed 6mo ago), licensed MIT. It adds 685 tokens to every session, about $0.0034 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-09-04.

Related

Other instructions, from other repositories

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.

openai/codex · 5,182 tokens

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).

microsoft/vscode · 6,785 tokens

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.

vercel/next.js · 7,296 tokens

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.

langchain-ai/langchain · 4,469 tokens

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).

microsoft/vscode · 5,001 tokens

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.

github/spec-kit · 7,104 tokens