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/1jehuang/jcode/agents-mdgit clone --depth 1 https://github.com/1jehuang/jcodeWhat 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.00633 | $0.00633 |
| Opus 5 | $0.00316 | $0.00316 |
| Sonnet 5 | $0.00127 | $0.00127 |
| Haiku 4.5 | $0.00063 | $0.00063 |
Grade A, and why
jcode 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.
How it starts
The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Development Workflow
- Stay on your own branch - Do not take, cherry-pick, merge, or copy code from other
people's or other agents' branches unless the source branch belongs to a repository
maintainer and the user explicitly asks you to integrate it. Only work from your branch
and its base (e.g.
main) otherwise. Never integrate branches owned by non-maintainers or other agents yourself; tell the user and let them decide how to proceed.
Install Notes
~/.local/bin/jcodeis the launcher symlink used fromPATH.~/.jcode/builds/current/jcodeis the active local/source-build channel; self-dev builds andscripts/install_release.shpoint the launcher here.~/.jcode/builds/stable/jcodeis the stable release channel;scripts/install.shinstalls this and points the launcher here.~/.jcode/builds/versions/<version>/jcodestores immutable binaries.~/.jcode/builds/canary/jcodestill exists for canary/testing flows, but it is not the primary self-dev install path.- On Windows, the equivalents are
%LOCALAPPDATA%\\jcode\\bin\\jcode.exefor the launcher,%LOCALAPPDATA%\\jcode\\builds\\stable\\jcode.exefor stable, and%LOCALAPPDATA%\\jcode\\builds\\versions\\<version>\\jcode.exefor immutable installs;scripts/install.ps1currently installs the stable channel. - Ensure
~/.local/binis before~/.cargo/bininPATH.
Verifying a change at runtime
cargo build alone proves nothing about behavior. jcode run and interactive
sessions are served by the long-lived daemon at
~/.jcode/builds/shared-server/jcode, which is a symlink into
~/.jcode/builds/versions/<version>/. Until that symlink is repointed and the
daemon restarted (jcode self-dev --build), a freshly built binary is inert and
every runtime check silently measures the old code.
To test a change without disturbing the shared daemon or the caller's session, run your build against its own socket:
cargo build --profile selfdev
./target/selfdev/jcode run --no-update --socket /run/user/1000/jcode-mytest.sock '<prompt>'
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 · 45 lines · 633 tokens per session scan A 23f9a0f60466
jcode AGENTS.md is an instructions file published in the GitHub repository 1jehuang/jcode (18,821 stars, last pushed 3d ago), licensed MIT. It adds 633 tokens to every session, about $0.0032 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
dsh-TUI AGENTS.md
AGENTS.md instructions for ccch1mneyyy/dsh-TUI, covering agents.md, 仓库布局, 命令, 上游边界与契约 and 约定与红线.
golembot CLAUDE.md
Instructions for 0xranx/golembot, covering golembot — project conventions for claude code, architecture hard constraints, things you must never do, interface change rules and file responsibility boundaries.
sortie copilot-instructions.md
Instructions for sortie-ai/sortie, covering sortie coding & review standards, 1. layered imports (downward only; violation is critical), 2. concurrency safety, 3. workspace path safety (critical: security boundary) and 4. persistence (sqlite).
copperhead CLAUDE.md
Instructions for copperheadhq/copperhead, covering claude.md, what this repo is, sources of truth, workflow (openspec) and architecture (per spec.md §2).
pi-ask AGENTS.md
Instructions for eko24ive/pi-ask, covering agents.md, project scope, project goals, tech stack and commands.
amp-acp AGENTS.md
Instructions for tao12345666333/amp-acp, covering agents.md, commands, architecture and code style.