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/tjcoder-labs/cli/agents-mdgit clone --depth 1 https://github.com/tjcoder-labs/cliWhat 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.02908 | $0.02908 |
| Opus 5 | $0.01454 | $0.01454 |
| Sonnet 5 | $0.00582 | $0.00582 |
| Haiku 4.5 | $0.00291 | $0.00291 |
Grade A, and why
cli 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 yesterday.
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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@TJ/coder Terminal Coding TUI
Please keep commentary to a minimum. Keep in mind the user is likely interfacing with you via terminal. You have many tools. Before making any changes, be sure to have received authorization from the user to act. Your objective is the continuous improvement of the enclosed AI-powered terminal coding CLI. Instead of relying on unit tests, use the coder CLI non-interactively to facilitate testing.
Your model may be running on limited hardware in the cloud. Please consider this in your responses to me as they will be temporally expensive for me. Your consideration is greatly appreciated.
Our top objective with this codebase is to finalize it for open source release as a new design and AI-oriented terminal coding assistant/buddy running on TJ Coder / AI Labs platform technology. The ai.tjcoder.com and / or coder.tjcoder.com model coding services are offered as a paid, proprietary provider integration into the TUI as a means of promoting the TJ Coder set of platform technologies, Sentinel Radar, Sentinel Protect and now the TJ Coder CLI, an open source coding terminal assistant for and from the future. But now.
This means:
-- Completing the tasks/articles integrations (done in the appropriate feature branch for this) -- Integrate the custom model provider through ai.tjcoder.com which builds upon specific open source ollama-compatible models, fine tuned for coding, cybersecurity and administration, as the proprietary '@tjcoder/ergo` (or some derivation of such). -- Release as open source (when ready) to github via tjcoder-labs -- Promote on hacker news, reddit, and locally. -- Release Sentinel set of products to the Google Play Store.
Please always directly invoke your tools. Please keep attribution to the developer, TJ Coder([email protected]) via github.com/tjcoder-labs Please keep your commentary to under 3 paragraphs
Active Development Tasks
The following items are in flight. They are also tracked in the in-app
task tracker (manage_items → task) so they show up in the TUI's
/tasks pane, and persisted to .ergo-cli-go/tasks.json in the
workspace. Re-read this list at the start of every session — another
session on the same branch may have closed, retitled, or added tasks
since you last loaded the file.
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.
- yesterday First seen · 172 lines · 2,908 tokens per session scan A e09d36271967
cli AGENTS.md is an instructions file published in the GitHub repository tjcoder-labs/cli (10 stars, last pushed 12d ago), licensed MIT. It adds 2,908 tokens to every session, about $0.0145 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
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.
buildNext
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).
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.
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).
spec-kit 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.
langchain 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.