Borrowing it
Nothing to install: this file belongs to kei-prog/shikigami. 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/kei-prog/shikigami/main/AGENTS.mdgit clone --depth 1 https://github.com/kei-prog/shikigamiWrote 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/kei-prog/shikigami/agents-md)<a href="https://agentmods.dev/instructions/kei-prog/shikigami/agents-md"><img src="https://agentmods.dev/badge/instructions/kei-prog/shikigami/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.1 | $0.00723 | $0.00723 |
| Opus 5 | $0.00362 | $0.00362 |
| Sonnet 5 | $0.00145 | $0.00145 |
| Haiku 4.5 | $0.00072 | $0.00072 |
Grade A, and why
shikigami 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 5d 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
shikigami is a Rust 2024 TUI for managing Codex CLI threads across Git repositories. The entry point is src/main.rs; application state lives in src/app.rs, rendering in src/ui.rs, and App Server JSONL communication in src/app_server.rs. Repository discovery, thread data, Git worktrees, chat state, and clipboard support use correspondingly named modules. Tests are colocated in #[cfg(test)] mod tests blocks. Never commit generated target/ contents.
Product Scope & Feature Decisions
Shikigami enables powerful multi-threaded Codex use that the Codex CLI alone cannot provide. Keep responsibilities that Codex can perform through natural-language instructions, tools, or skills in Codex; do not reimplement them as built-in Shikigami workflows by default. Concentrate Shikigami on persistent client capabilities such as coordinating and navigating multiple threads, repositories, and worktrees, and making their state clear to the user.
Before adding a feature, determine whether Codex or a skill can already provide it sufficiently and whether it creates value unavailable in the Codex CLI itself. If both answers favor existing Codex capabilities, leave the feature to Codex. Prefer changes that reduce the human interaction and coordination cost of operating multiple concurrent Codex threads.
Build, Test, and Development Commands
Run shell commands through rtk in this workspace:
rtk cargo runlaunches the TUI; Codex CLI and Git must be installed.rtk cargo buildcompiles a debug binary.rtk cargo testruns the full unit-test suite.rtk cargo fmt --checkverifies standard Rust formatting.rtk cargo clippy --all-targets --all-features -- -D warningscatches lint issues and treats warnings as failures.rtk cargo install --path .installs the localshiexecutable.
Prefer lightweight implementations. Verify performance-sensitive changes with before/after measurements.
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.
- 5d ago First seen · 41 lines · 723 tokens per session scan A c48c8abb5035
shikigami AGENTS.md is an instructions file published in the GitHub repository kei-prog/shikigami (1 stars, last pushed 23d ago), licensed MIT. It adds 723 tokens to every session, about $0.0036 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
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.
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.
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).
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).
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.
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.