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/jidoka/agents-mdgit clone --depth 1 https://github.com/agentjido/jidokaWrote 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/jidoka/agents-md)<a href="https://agentmods.dev/instructions/agentjido/jidoka/agents-md"><img src="https://agentmods.dev/badge/instructions/agentjido/jidoka/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.00196 | $0.00196 |
| Opus 5 | $0.00098 | $0.00098 |
| Sonnet 5 | $0.00039 | $0.00039 |
| Haiku 4.5 | $0.00020 | $0.00020 |
Grade A, and why
jidoka 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 - Jidoka
Intent
This directory contains the official Jidoka package. The public module
namespace is Jidoka. The public architecture is documented in guides/.
Working Rules
- Keep this package focused on the documented Jidoka architecture.
- Preserve the functional-core/effect-shell boundary:
- pure data transitions in
Jidoka.Workflow.Steps; - external effects through
Jidoka.Effect.Intent; - adapter calls through
Jidoka.Runtime.EffectInterpreter.
- pure data transitions in
- Do not reintroduce
Jido.AI.ReActas the owner of the agent loop. - Keep tests deterministic with injected runtime capabilities.
Commands
mix deps.getmix formatmix test
Release Hygiene
- Do not modify
CHANGELOG.md; release notes are generated from Git history during release, so keep changes focused on proper Conventional Commits.
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 · 27 lines · 196 tokens per session scan A fb5d497cb9d8
jidoka AGENTS.md is an instructions file published in the GitHub repository agentjido/jidoka (42 stars, last pushed 2d ago), licensed Apache-2.0. It adds 196 tokens to every session, about $0.0010 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 AGENTS.md
AGENTS.md instructions for agentjido/jido, covering agents.md - jido guide, intent, runtime baseline, commands and architecture snapshot.
jido_ai AGENTS.md
Instructions for agentjido/jido_ai, covering agents.md - jido.ai guide, intent, runtime baseline, commands and architecture snapshot.
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.
kungfu copilot-instructions.md
Copilot instructions for kungfu-systems/kungfu: Read and follow AGENTS.md before proposing or running changes. It is the shared agent router for this repository, including the canonical Shifu development and build entrypoint.
pixir CLAUDE.md
Instructions for Ranvier-Technologies/pixir, covering pixir harness - legacy agent guide, current map and commands.
sprites-ex CLAUDE.md
Claude Code instructions for superfly/sprites-ex, covering sprites elixir sdk, quick reference, common commands, install dependencies and compile.