jayrah AGENTS.md

Repository instructions for jayrah, a Python project with command-line and web interfaces. They cover its folders, development commands, coding style, configuration, and tests.

In plain words
What is it for?
Use them when working on jayrah to find the right modules, run tests or linting, format code, start the web interface, and follow its Python conventions.
Why use it?
They give a coding agent the project rules needed to make consistent changes and run the expected checks.

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

Made for: Codex, OpenCode.

Per session 670 This file is loaded in full into every session.
When invoked 670 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.00670 $0.00670
Opus 5 $0.00335 $0.00335
Sonnet 5 $0.00134 $0.00134
Haiku 4.5 $0.00067 $0.00067

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

Security

Grade A, and why

jayrah 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 · 54 lines

How it starts

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

Repository Guidelines

Project Structure & Module Organization

  • Source: jayrah/ (entrypoint jayrah.cli:main). Key modules: api/, commands/, ui/ (TUI + ui/web/), config/, utils/.
  • Tests: tests/ with test_*.py modules and conftest.py.
  • Tooling: pyproject.toml (deps and scripts), Makefile (common tasks), .pre-commit-config.yaml (lint/test hooks).
  • Config: user settings in ~/.config/jayrah/config.yaml.

Build, Test, and Development Commands

Use uv and Makefile targets:

make sync           # Install deps via uv
make test           # Run pytest (verbose)
make lint           # Run pylint + ruff check
make format         # Format with ruff
make coverage       # Pytest coverage (HTML in ./htmlcov)
uv run jayrah ...   # Run CLI locally (e.g., browse)
make web            # Start web UI at http://127.0.0.1:8000

Coding Style & Naming Conventions

  • Language: Python 3.12. Indent 4 spaces, UTF-8 files.
  • Style: format with ruff format; lint with ruff and pylint.
  • Naming: packages/modules lower_snake_case; classes PascalCase; functions/vars snake_case.
  • Imports: prefer absolute within jayrah.*.
  • Keep CLI user messages concise; centralize logic under api/ and utils/.

Testing Guidelines

  • Framework: pytest (+ pytest-asyncio, pytest-cov).
  • Location: add tests under tests/ named test_<area>.py; test functions test_<behavior>().
  • Coverage: add regression tests for bugs; aim for meaningful coverage (see make coverage).
  • Running examples:
uv run pytest -k mcp -vv
uv run pytest tests/test_commands.py::test_browse

Commit & Pull Request Guidelines

  • Commits: follow Conventional Commits seen in history (e.g., feat: ..., fix: ..., refactor: ...).
  • PRs: clear description, linked issues, reproduction steps, and screenshots/GIFs for UI.
  • CI hygiene: run make lint test format locally; ensure pre-commit passes.
  • Scope: keep PRs focused; update README or docs when behavior changes.

Read the full file on GitHub · 54 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 · 54 lines · 670 tokens per session scan A 6934bf4a9f22

Subscribe to this mod's changes

jayrah AGENTS.md is an instructions file published in the GitHub repository chmouel/jayrah (3 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 670 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-08-31.