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/nomadamas/jikji/agents-mdgit clone --depth 1 https://github.com/NomaDamas/jikjiWrote 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/nomadamas/jikji/agents-md)<a href="https://agentmods.dev/instructions/nomadamas/jikji/agents-md"><img src="https://agentmods.dev/badge/instructions/nomadamas/jikji/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.01101 | $0.01101 |
| Opus 5 | $0.00550 | $0.00550 |
| Sonnet 5 | $0.00220 | $0.00220 |
| Haiku 4.5 | $0.00110 | $0.00110 |
Grade A, and why
jikji 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.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jikji project guide
Jikji is a separate project from Folder1004.
Product identity
- Jikji prepares local folders for AI-agent discovery without moving, renaming, or deleting user files.
- It creates text-first knowledge maps and parser caches under
.jikji/plus a root.jikji_agent_map.md(legacy000_JIKJI_AGENT_MAP.md). - It is meant to be used by local agents such as Hermes/Codex through CLI commands or skills.
- Folder1004 remains the GUI product for physically organizing messy Desktop/Downloads-style folders.
Safety boundary
- Default and expected behavior is non-destructive.
- Never reorganize user folders in this repo unless a future feature explicitly adds a separate, warned physical mode.
.jikji/and.jikji_agent_map.mdare generated artifacts and may be regenerated.
Generated artifact ownership
Jikji may regenerate only its documented artifacts: .jikji/manifest.json, .jikji/*.jsonl, .jikji/search_index.sqlite, .jikji/agent_map.md, .jikji/agent_routes.md, .jikji/agent_skill_context.md, .jikji/human_guide.md, .jikji/autorag_manifest.json, .jikji/corpus_profile.json, .jikji/intent_taxonomy.json, .jikji/knowledge_graph.json, .jikji/llm_wiki_schema.md, .jikji/wiki/, .jikji/wiki/sources/, .jikji/doc_text/, .jikji/doc_meta/, .jikji/eval/, .jikji/.lock, root .jikji_agent_map.md (legacy 000_JIKJI_AGENT_MAP.md), and Jikji routing blocks inside AGENTS.md, CLAUDE.md, and .cursorrules. Retired generated artifacts listed in manifest.json under retired_cleanup_paths may be removed during prepare. Do not delete arbitrary user-created files under .jikji/.
Local-agent standard docs live in docs/local-agent-search-standard.md, docs/schema.md, and docs/agent-usage.md.
Repository layout
crates/contains the Rust workspace and shipped CLI.python/jikji/contains the Python package for reference behavior, benchmarks, golden capture, and optional media support.tests/parity/,tests/golden/, andtools/parity/are cross-stack parity assets shared by Rust and Python.- Root
pyproject.tomlis workspace/tooling configuration; Python package metadata lives inpython/jikji/pyproject.toml.
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 · 65 lines · 1,101 tokens per session scan A 8c2ceafbdde8
jikji AGENTS.md is an instructions file published in the GitHub repository NomaDamas/jikji (42 stars, last pushed 9d ago), licensed MIT. It adds 1,101 tokens to every session, about $0.0055 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
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.