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/doist/todoist-cli/agents-mdgit clone --depth 1 https://github.com/Doist/todoist-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.01210 | $0.01210 |
| Opus 5 | $0.00605 | $0.00605 |
| Sonnet 5 | $0.00242 | $0.00242 |
| Haiku 4.5 | $0.00121 | $0.00121 |
Grade B, and why
todoist-cli AGENTS.md scanned grade B with 1 finding 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
node dist/index.js <command> ... # run any command How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Todoist CLI
For repo structure, where things live, and shared utilities, read CODEBASE.md first. This file covers the rules; CODEBASE.md is the map.
TypeScript CLI for Todoist. Binary name: td.
Build & Run
npm run build # compile TypeScript (uses tsconfig.build.json, excludes tests)
npm run dev # watch mode (uses tsconfig.build.json)
npm run type-check # type check source + tests (uses tsconfig.json)
npm run check # lint + format check
npm run fix # auto-fix lint + format
npm test # run tests
Two-tsconfig setup: tsconfig.json includes both source and test files — used by type-check and IDEs. tsconfig.build.json extends it but excludes colocated *.test.ts files plus src/test-support/ — used by build and dev to keep test-only code out of dist/.
Run the CLI directly (no linking needed):
node dist/index.js --help # show commands
node dist/index.js today # run 'today' command
node dist/index.js <command> ... # run any command
Use this to verify changes work before committing.
Rules when changing code
- Named flag aliases: where commands accept positional args for context (project, task, workspace), named flags (
--project,--task,--workspace) are also accepted. Error if both positional and flag are provided. - Implicit
viewsubcommand edge case:td project <ref>defaults totd project view <ref>. If a project/task name matches a subcommand name (e.g.,"list"), the subcommand wins — users must usetd project view list. - API response shape: client returns
{ results: T[], nextCursor? }— always destructure. - Priority mapping: CLI uses
"p1"–"p4"strings; API uses 4=p1 (highest), 1=p4 (lowest). UseparsePriorityfromsrc/lib/task-list.ts, never hand-roll. - Errors: throw
CliError(code, message, hints?)fromsrc/lib/errors.tsfor anything user-facing. The globalparseAsync().catchinsrc/index.tsrenders it correctly in JSON and pretty modes. The same handler also matchesBaseCliError(re-exported fromsrc/lib/errors.ts) so errors thrown by@doist/cli-corehelpers route through the same formatter.
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 · 100 lines · 1,210 tokens per session scan B 6fa6806acd85
todoist-cli AGENTS.md is an instructions file published in the GitHub repository Doist/todoist-cli (300 stars, last pushed 4d ago), licensed MIT. It adds 1,210 tokens to every session, about $0.0060 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
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.
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).
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.
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).
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.