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/tninja/ai-code-interface.el/copilot-instructionsgit clone --depth 1 https://github.com/tninja/ai-code-interface.elWhat 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.01289 | $0.01289 |
| Opus 5 | $0.00645 | $0.00645 |
| Sonnet 5 | $0.00258 | $0.00258 |
| Haiku 4.5 | $0.00129 | $0.00129 |
Grade A, and why
ai-code-interface.el copilot-instructions.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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Copilot Instructions for ai-code-interface.el
Project Overview
This is ai-code-interface.el, an Emacs package that provides a uniform interface for AI-assisted software development across pluggable AI coding backends.
Language and Technology
- Language: Emacs Lisp
- Package System: Emacs package with
use-packagesupport - Version Control: Git with Magit integration
- Testing Framework: ERT (Emacs Lisp Regression Testing)
Code Style and Conventions
File Naming
- Main module:
ai-code.el - Sub-modules:
ai-code-*.el(e.g.,ai-code-backends.el,ai-code-agile.el) - Tests:
test_*.el(e.g.,test_ai-code-change.el)
Emacs Lisp Conventions
- Use
lexical-binding: tin all files - Follow standard Emacs Lisp naming conventions:
- Public functions:
ai-code-function-name - Private functions:
ai-code--function-name(double dash prefix) - Custom variables:
ai-code-variable-name
- Public functions:
- Include proper header comments with:
- Author
- Version (when applicable)
- Package-Requires
- SPDX-License-Identifier: Apache-2.0
- Commentary section
- Use
declare-functionfor forward declarations - Prefer
defcustomfor user-configurable variables - Use
;;;###autoloadcookies for interactive commands
Code Organization
- Group related functionality in separate modules
- Use
requirestatements at the beginning of files - Maintain clear separation between backend implementations and interface code
Testing
Running Tests
- Tests use ERT (Emacs Lisp Regression Testing)
- Test files are named with
test_prefix - Run tests with:
emacs -batch -l ert -l <test-file>.el -f ert-run-tests-batch-and-exit
Test Conventions
- Use
ert-deftestfor defining tests - Test names should be descriptive:
test-module--function-name-scenario - Use
with-temp-bufferfor testing buffer-related functionality - Mock external dependencies with
cl-letfwhen needed
Byte-compilation warnings
- Treat new byte-compilation warnings as regressions when touching Emacs Lisp code.
- For documentation hygiene on touched files, also run
M-x checkdoc(or batchcheckdoc-file) before wrapping up changes.
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 · 148 lines · 1,289 tokens per session scan A 49804dc3a61c
ai-code-interface.el copilot-instructions.md is an instructions file published in the GitHub repository tninja/ai-code-interface.el (274 stars, last pushed 4d ago), licensed Apache-2.0. It adds 1,289 tokens to every session, about $0.0064 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
codex-usage-widget AGENTS.md
Instructions for ognjeeen/codex-usage-widget, covering agents.md, project, scope and decision discipline, authorization and repository safety and architecture boundaries.
CodexClaw AGENTS.md
Instructions for MackDing/CodexClaw, covering repository guidelines, repo structure, start and dev commands, test commands and lint and format.
codex-loop-orchestra AGENTS.md
Instructions for LEO001020/codex-loop-orchestra, covering loop discipline, 1. decomposition discipline (single-pass plan-and-solve), 3. return convention (all subagents, mandatory), 4. recoverable compression directive and 5. kernel trigger rules (ipybox, when enabled).
codex-token-meter AGENTS.md
Instructions for prefect12/codex-token-meter, covering ai token meter development guide, project shape, build and verification, git workflow and ai token meter test loop.
ai-session-search AGENTS.md
Instructions for lililib/ai-session-search, a project described as: Local-first full-text search and reusable context library for AI coding sessions across Claude Code, Codex, Cursor, OpenCode, Copilot CLI, and more. Source sessions stay read-only.
codex-switch AGENTS.md
AGENTS.md instructions for ChArLiEdance/codex-switch, covering repository agents and platform isolation.