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/agentjido/jido_ai/agents-mdgit clone --depth 1 https://github.com/agentjido/jido_aiWrote 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/agentjido/jido_ai/agents-md)<a href="https://agentmods.dev/instructions/agentjido/jido_ai/agents-md"><img src="https://agentmods.dev/badge/instructions/agentjido/jido_ai/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 | $0.00462 | $0.00462 |
| Opus 5 | $0.00231 | $0.00231 |
| Sonnet 5 | $0.00092 | $0.00092 |
| Haiku 4.5 | $0.00046 | $0.00046 |
Grade A, and why
jido_ai 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 4d 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.
What it actually says
AGENTS.md - Jido.AI Guide
Intent
Build tool-using AI agents with explicit strategy, runtime policy, and reliable request orchestration.
Runtime Baseline
- Elixir
~> 1.18 - OTP
27+(release QA baseline)
Commands
mix test(default alias excludes:flaky)mix test.fast(stable smoke suite)mix precommit(format,compile --warnings-as-errors,doctor --summary --raise,test.fast)mix qormix quality(format,compile,credo,doctor,dialyzer)mix docs
Architecture Snapshot
Jido.AI.Agent+ strategy agents (CoD,CoT,AoT,ToT,GoT,TRM,Adaptive)Jido.AI.Actions.*: reusable runtime actions for chat/tool/structured flows- ReqLLM integration for provider abstraction and model routing
- Policy/observability modules for retries, quotas, telemetry, and traceability
Standards
- Keep model selection, timeout, retry, and tool policy explicit
- Use Zoi-first schemas for tool inputs and structured outputs
- Keep provider-specific behavior behind ReqLLM integration boundaries
- Preserve tagged tuple and structured error contracts
- Prefer deterministic fallback behavior over ad-hoc prompt pipelines
Testing and QA
- Cover strategy behavior, tool-call loops, and error/fallback handling
- Keep flaky tests isolated behind tags; maintain a stable smoke subset (
mix test.fast) - Validate public examples/scripts when runtime behavior changes
Release Hygiene
- Keep semver ranges stable (
~> 2.0ecosystem peers; package currently2.0.0-rc.0) - Use Conventional Commits
- Do not modify
CHANGELOG.md; release notes are generated from Git history during release, so keep changes focused on proper Conventional Commits. - Update guides and migration notes for behavior/API changes
References
README.mdusage-rules.mdguides/- https://hexdocs.pm/jido_ai
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.
- 4d ago First seen · 46 lines · 462 tokens per session scan A 22db4d39a498
jido_ai AGENTS.md is an instructions file published in the GitHub repository agentjido/jido_ai (203 stars, last pushed 6d ago), licensed Apache-2.0. It adds 462 tokens to every session, about $0.0023 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
jido_managed_agents AGENTS.md
AGENTS.md instructions for agentjido/jido_managed_agents, covering project guidelines, phoenix v1.8 guidelines, js and css guidelines, ui/ux & design guidelines and release hygiene.
opal AGENTS.md
Instructions for matteing/opal, covering opal project guide, architecture, components, built-in tools and development.
jidoka AGENTS.md
AGENTS.md instructions for agentjido/jidoka, covering agents.md - jidoka, intent, working rules, commands and release hygiene.
conduit_mcp CLAUDE.md
Instructions for nyo16/conduit_mcp, covering claude.md, project overview, build & test commands, architecture and request flow.
loomkin AGENTS.md
Instructions for pass-agent/loomkin, covering loomkin - ai instructions, monorepo layout, authentication, routes that require authentication and routes that work with or without authentication.
loomkin copilot-instructions.md
Instructions for pass-agent/loomkin: Read and follow CONTRIBUTING.md for all conventions, including commit message format, build commands, and code style.