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/uhop/console-toolkit/agents-mdgit clone --depth 1 https://github.com/uhop/console-toolkitWhat 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.00966 | $0.00966 |
| Opus 5 | $0.00483 | $0.00483 |
| Sonnet 5 | $0.00193 | $0.00193 |
| Haiku 4.5 | $0.00097 | $0.00097 |
Grade A, and why
console-toolkit 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
console-toolkit — AI Agent Rules
Project identity
console-toolkit is a zero-dependency ESM JavaScript library for rich CLI/TUI output: styled text, boxes, panels, tables, charts, plots, turtle graphics, and spinners. Node.js 22+, Bun, Deno.
Critical rules
- ESM-only. All imports must use
.jsextensions:import Box from './box.js'. - No runtime dependencies. Never add packages to
dependencies. OnlydevDependenciesare allowed. - No build step. Source JS in
src/is shipped directly. Do not create build scripts or compiled output. - Hand-written
.d.tsfiles. They are NOT generated. When modifying a public API, update both the.jsand.d.tsfiles. - No JSDoc in
.jsfiles. API contracts live in the sidecar.d.tsonly. Don't add/** ... */blocks tosrc/*.js; they duplicate the.d.tsand rot out of sync. - Do not modify or delete test expectations without understanding why they changed.
Code style
- Prettier: 120 char width, single quotes, no bracket spacing, no trailing commas, arrow parens "avoid".
- 2-space indentation (
.editorconfig). - Imports at top of file. No dynamic imports unless necessary.
- Comments are why-markers only — a non-trivial decision/constraint or an algorithm reference; never narration of what the code does. Type docs live in the
.d.ts, not as JSDoc in.js.
Architecture quick reference
Boxis immutable — methods return newBoxinstances.Panelis mutable — methods mutatethisand returnthisfor chaining.- Method aliases use
addAlias/addAliasesfrommeta.js. pad(t, r, b, l)follows CSS shorthand order.- Three text containers convert between each other:
strings(string[]),Box,Panel. - SGR styling:
Styleclass with fluent API;s/ctagged template literals.
Writing tests
Tests use tape-six. For the full testing API, patterns, and conventions see node_modules/tape-six/TESTING.md.
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 · 68 lines · 966 tokens per session scan A e383ee37fd4d
console-toolkit AGENTS.md is an instructions file published in the GitHub repository uhop/console-toolkit (10 stars, last pushed 1mo ago), licensed BSD-3-Clause. It adds 966 tokens to every session, about $0.0048 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
microcharts AGENTS.md
Instructions for ganapativs/microcharts: Single source of truth: CLAUDE.md. All non-negotiables, stack picks, architecture map, catalog rules, quality bar, roadmap position, and session working rules live there — read it in full before any work. CONTRIBUTING.md covers what the project takes (bug fixes and fixes to…
microcharts CLAUDE.md
Instructions for ganapativs/microcharts, covering microcharts — contributor & agent guide, design principles, non-negotiables (violating any of these is a bug), not shipped (by design) and stack.
recharts AGENTS.md
Instructions for recharts/recharts: This is Recharts repository. Recharts is a React-based charting library. The goal is to provide a simple, declarative, and composable way to build charts. We value consistency, usability, and performance. Accessibility is important.
joint CLAUDE.md
Instructions for clientIO/joint, covering claude.md, project overview, common commands, install dependencies and build distribution files (runs grunt).
ShipSwift AGENTS.md
Instructions for signerlabs/ShipSwift, covering agents.md, project overview, directory structure, naming conventions and dependency rules.
VChart AGENTS.md
Instructions for VisActor/VChart, covering vchart 工程基准, 编码习惯, 文档规范 and 优先级.