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.
npx agentmods add instructions/chmouel/jayrah/agents-mdgit clone --depth 1 https://github.com/chmouel/jayrahWhat 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 | $0.00670 | $0.00670 |
| Opus 5 | $0.00335 | $0.00335 |
| Sonnet 5 | $0.00134 | $0.00134 |
| Haiku 4.5 | $0.00067 | $0.00067 |
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.
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/(entrypointjayrah.cli:main). Key modules:api/,commands/,ui/(TUI +ui/web/),config/,utils/. - Tests:
tests/withtest_*.pymodules andconftest.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 withruffandpylint. - Naming: packages/modules
lower_snake_case; classesPascalCase; functions/varssnake_case. - Imports: prefer absolute within
jayrah.*. - Keep CLI user messages concise; centralize logic under
api/andutils/.
Testing Guidelines
- Framework:
pytest(+pytest-asyncio,pytest-cov). - Location: add tests under
tests/namedtest_<area>.py; test functionstest_<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 formatlocally; ensurepre-commitpasses. - Scope: keep PRs focused; update README or docs when behavior 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.
- 2d ago First seen · 54 lines · 670 tokens per session scan A 6934bf4a9f22
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.
Other instructions, from other repositories
mcp-jira-stdio AGENTS.md
Instructions for freema/mcp-jira-stdio, covering repository guidelines, project structure & modules, build, test, and development, coding style & naming and adding a tool.
ultra-jira-mcp CLAUDE.md
Instructions for criblio/ultra-jira-mcp, covering ultra-jira-mcp — agent guide, layout, mental model, two modes — pick the right one and what lives where (toolkit vs. this repo).
ultra-jira-mcp AGENTS.md
Instructions for criblio/ultra-jira-mcp, covering agents.md and quick reference.
intervals-icu-mcp CLAUDE.md
Instructions for hhopke/intervals-icu-mcp, covering claude.md, project overview, development commands, architecture (quick reference) and tool categories.
ai-toolkit AGENTS.md
Instructions for pipefy/ai-toolkit, covering repository guidelines, documentation map, project structure, import namespace migration: pipefysdk → pipefy and src/pipefysdk/init.py (transitional shim).
flyto-core CLAUDE.md
Instructions for flytohub/flyto-core, covering claude notes, cross-agent handoff and shared code intelligence.