planner AGENTS.md

A repository guide for codebar planner, a Rails application that manages coding workshops, members, events, registrations, invitations, RSVPs, and feedback. It documents the required workflow, including feature branches and pull requests, which are proposed changes reviewed before merging.

In plain words
What is it for?
Use it when planning or implementing codebar planner changes, setting up development, creating feature branches, and preparing pull requests.
Why use it?
It tells coding agents how the project works and how changes must be made, helping prevent direct changes to the master branch or unapproved merges.

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/codebar/planner/agents-md
Clone the repo
git clone --depth 1 https://github.com/codebar/planner

Made for: Codex, OpenCode.

Per session 2,868 This file is loaded in full into every session.
When invoked 2,868 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.02868 $0.02868
Opus 5 $0.01434 $0.01434
Sonnet 5 $0.00574 $0.00574
Haiku 4.5 $0.00287 $0.00287

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

Security

Grade A, and why

planner 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 yesterday.

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 · 326 lines

How it starts

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

AGENTS.md

This file provides guidance to AI agents when working with code in this repository.

Project Overview

codebar planner is a Rails 8.1 application for managing codebar.io members and events. It handles workshop/event scheduling, member registration, invitations, RSVPs, and feedback collection for coding workshops organized by codebar chapters.

Development Workflow

CRITICAL: Never work directly on the master branch. All changes must be made via pull requests from feature branches.

Branching Strategy

  1. Create a feature branch from master: git checkout -b feature/descriptive-name
  2. Make your changes and commit them to the feature branch
  3. Push the branch to the remote repository
  4. Create a pull request for review
  5. Wait for approval before merging to master

Never:

  • Commit directly to master
  • Push directly to master
  • Merge without review

Development Setup

IMPORTANT: Always use native installation with bundle exec commands. Never use Docker or bin/d* commands.

Prerequisites

  • mise — install via brew install mise, then enable mise activate in your shell profile (see mise docs). Alternatively, use mise exec to run commands with project env vars without shell activation.
  • PostgreSQL running locally (default port 5432, or configure via DB_PORT)

Native Installation

cp mise.local.toml.example mise.local.toml
# Edit mise.local.toml with your GitHub OAuth credentials
# Optionally delete .env if it exists from a prior setup:
rm .env
bundle && rake db:create db:prepare db:seed
  • Server: bundle exec rails server
  • Tests: make test or bundle exec parallel_rspec spec/ -n 3 - runs RSpec tests in parallel (3 processes is optimal)
  • Single test: bundle exec rspec spec/path/to/file_spec.rb:42
  • Rails console: bundle exec rails console
  • Run rake tasks: bundle exec rake [task]
  • Linting: bundle exec rubocop

Read the full file on GitHub · 326 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. yesterday First seen · 326 lines · 2,868 tokens per session scan A ea31007841c9

Subscribe to this mod's changes

planner AGENTS.md is an instructions file published in the GitHub repository codebar/planner (104 stars, last pushed yesterday), licensed MIT. It adds 2,868 tokens to every session, about $0.0143 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.