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/sunjiawe/task-cli/gemini-mdgit clone --depth 1 https://github.com/sunjiawe/task-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.13771 | $0.13771 |
| Opus 5 | $0.06885 | $0.06885 |
| Sonnet 5 | $0.02754 | $0.02754 |
| Haiku 4.5 | $0.01377 | $0.01377 |
Grade A, and why
task-cli GEMINI.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 — 1,669 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agentic Coding: Humans Design, Agents code!
If you are an AI agent involved in building LLM Systems, read this guide VERY, VERY carefully! This is the most important chapter in the entire document. Throughout development, you should always (1) start with a small and simple solution, (2) design at a high level (
docs/design.md) before implementation, and (3) frequently ask humans for feedback and clarification. {: .warning }
Agentic Coding Steps
Agentic Coding should be a collaboration between Human System Design and Agent Implementation:
| Steps | Human | AI | Comment |
|---|---|---|---|
| 1. Requirements | ★★★ High | ★☆☆ Low | Humans understand the requirements and context. |
| 2. Flow | ★★☆ Medium | ★★☆ Medium | Humans specify the high-level design, and the AI fills in the details. |
| 3. Utilities | ★★☆ Medium | ★★☆ Medium | Humans provide available external APIs and integrations, and the AI helps with implementation. |
| 4. Data | ★☆☆ Low | ★★★ High | AI designs the data schema, and humans verify. |
| 5. Node | ★☆☆ Low | ★★★ High | The AI helps design the node based on the flow. |
| 6. Implementation | ★☆☆ Low | ★★★ High | The AI implements the flow based on the design. |
| 7. Optimization | ★★☆ Medium | ★★☆ Medium | Humans evaluate the results, and the AI helps optimize. |
| 8. Reliability | ★☆☆ Low | ★★★ High | The AI writes test cases and addresses corner cases. |
- Requirements: Clarify the requirements for your project, and evaluate whether an AI system is a good fit.
- Understand AI systems' strengths and limitations:
- Good for: Routine tasks requiring common sense (filling forms, replying to emails)
- Good for: Creative tasks with well-defined inputs (building slides, writing SQL)
- Not good for: Ambiguous problems requiring complex decision-making (business strategy, startup planning)
- Keep It User-Centric: Explain the "problem" from the user's perspective rather than just listing features.
- Balance complexity vs. impact: Aim to deliver the highest value features with minimal complexity early.
- Understand AI systems' strengths and limitations:
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 · 1,669 lines · 13,771 tokens per session scan A 272ad8abf3cc
task-cli GEMINI.md is an instructions file published in the GitHub repository sunjiawe/task-cli (2 stars, last pushed 1y ago), licensed Apache-2.0. It adds 13,771 tokens to every session, about $0.0689 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
gantt AGENTS.md
Instructions for DHTMLX/gantt, covering agents.md, what this is, layout, commands and working on the code.
single-file-wbs CLAUDE.md
Instructions for piguo45/single-file-wbs, covering wbs ツール - claude.md, 製品ビジョン・設計指針(#67), 取り扱いの原則(重要), アーカイブ運用(過去タスクの整理) and 動作環境.
operator CLAUDE.md
Instructions for untra/operator, covering claude.md - operator, project overview, tech stack, code style and plans & specs location.
FlowBoard AGENTS.md
Instructions for rasimme/FlowBoard, covering flowboard — agent entry point, start here and where things live.
STAR AGENTS.md
Instructions for wanghao9610/STAR, covering agent instructions, 1. think before coding, 2. simplicity first, 3. surgical changes and 4. goal-driven execution.
AllBeads CLAUDE.md
Instructions for thrashr888/AllBeads, covering claude.md, project overview, what allbeads does, current state (v0.2.0) and rust development commands.