Jido is an Elixir framework for building autonomous agents and multi-agent workflows as ordinary Elixir and OTP software. It is for developers who need explicit state changes, event routing, coordinated actions, and supervised fault-tolerant runtimes; AI model integration is optional.
Borrowing it
Nothing to install: this file belongs to agentjido/jido. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/agentjido/jido/main/AGENTS.mdgit clone --depth 1 https://github.com/agentjido/jidoWrote 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/agents-md)<a href="https://agentmods.dev/instructions/agentjido/jido/agents-md"><img src="https://agentmods.dev/badge/instructions/agentjido/jido/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/agentjido/jido/agents-md"><img src="https://agentmods.dev/badge/instructions/agentjido/jido/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00480 | $0.00480 |
| Opus 5.5 | $0.00192 | $0.00192 |
| Sonnet 5.5 | $0.00096 | $0.00096 |
| Haiku 4.5 | $0.00048 | $0.00048 |
Grade A, and why
jido 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 1mo 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 Guide
Intent
Build reliable agent systems by separating pure decision logic from runtime side-effect execution.
Runtime Baseline
- Elixir
~> 1.18 - OTP
27+(release QA baseline)
Commands
mix test(default alias excludes:flaky)mix test --include flaky(full suite)mix test --cover(coverage gate)mix qormix quality(format --check-formatted,compile --warnings-as-errors,credo,dialyzer)mix docs(local docs)
Architecture Snapshot
Jido.Agent: pure agent module with immutable state andcmd/2Jido.AgentServer: GenServer runtime for directives, lifecycle, and message flowJido.Agent.Directive.*: typed effect descriptors (Emit,SpawnAgent,StopChild, etc.)Jido.Agent.StateOp.*: internal state transition operations applied by strategy layer- Plugins/sensors provide capability composition without coupling core agent logic
Standards
- Keep
cmd/2pure: same input => same{agent, directives}output - Keep directives for external effects only; do not rely on directives for state mutation
- Use Zoi-first schemas for new agent/plugin/signal contracts
- Preserve tagged tuple and structured error contracts at public boundaries
- Keep cross-agent communication on signals/directives, not ad-hoc process messages
Testing and QA
- Prefer pure agent tests first, then AgentServer/runtime integration tests
- Use helpers from
test/AGENTS.md(JidoTest.Case,JidoTest.Eventually) for async assertions - Avoid
Process.sleep/1in tests; assert eventual state/event behavior
Release Hygiene
- Keep semver ranges stable (
~> 2.0for Jido ecosystem peers) - 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.
References
README.mdusage-rules.mdguides/test/AGENTS.md- https://hexdocs.pm/jido
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.
- 1mo ago Changed · -14 lines · -150 tokens per session e54d0021b3ff
- 2mo ago First seen · 61 lines · 630 tokens per session scan A b8b9f924af06
jido AGENTS.md is an instructions file published in the GitHub repository agentjido/jido (1,899 stars, last pushed 2d ago), licensed Apache-2.0. It adds 480 tokens to every session, about $0.0019 per session on Opus 5.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
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.