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_lib/agents-mdgit clone --depth 1 https://github.com/agentjido/jido_libWhat 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.00303 | $0.00303 |
| Opus 5 | $0.00151 | $0.00151 |
| Sonnet 5 | $0.00061 | $0.00061 |
| Haiku 4.5 | $0.00030 | $0.00030 |
Grade A, and why
jido_lib 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.
What it actually says
AGENTS.md — Jido Lib
Overview
jido_lib provides standard-library modules for the Jido ecosystem.
Current focus:
Jido.Lib.Github.Agents.IssueTriageBot(canonical signal-first API + Runic workflow orchestrator)
Namespace
All GitHub triage code lives under:
Jido.Lib.Github.Agents.*Jido.Lib.Github.Actions.*Jido.Lib.Github.Schema.*
Do not introduce generic shell abstractions in this package (for example Jido.Lib.Shell.Backend).
Shell backend abstractions belong in jido_shell.
Quality Requirements
- Elixir
~> 1.18 - Zoi schemas for public structs
- Splode for package-level error classification (
Jido.Lib.Error) mix qualityandmix testmust pass before commit- Public modules/functions must have docs and specs
Testing Guidance
- Keep unit tests deterministic with fake shell/session modules in
test/support/ - Keep live Sprite/GitHub tests under
@tag :integration - Ensure workflow tests validate node ordering, data pass-through, and teardown behavior
Workflow Spec
Canonical workflow documentation lives at:
docs/github_issue_triage_workflow.md
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.
- 2d ago First seen · 42 lines · 303 tokens per session scan A 32d5c08be0a5
jido_lib AGENTS.md is an instructions file published in the GitHub repository agentjido/jido_lib (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 303 tokens to every session, about $0.0015 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
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
Instructions for agentjido/jido_managed_agents, covering project guidelines, phoenix v1.8 guidelines, js and css guidelines, ui/ux & design guidelines and release hygiene.
koan AGENTS.md
AGENTS.md instructions for Anantys-oss/koan, covering agents.md, project overview, documentation first, wiki tooling and commands.
koan CLAUDE.md
Claude Code instructions for Anantys-oss/koan, covering claude.md, what is kōan, on-demand guidance (nested claude.md), specs discipline (mandatory) and documentation first.
koan copilot-instructions.md
Copilot instructions for Anantys-oss/koan, a project described as: Autonomous background agent that consumes unused Claude Max quota to explore, audit, and improve a codebase — communicating with its human via Telegram and a shared mission queue.
github-mcp-server copilot-instructions.md
Copilot instructions for github/github-mcp-server, covering github mcp server - copilot instructions, project overview, critical build & validation steps, required commands (run before committing) and when modifying mcp tools/endpoints.