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/dream-num/skills/agents-mdgit clone --depth 1 https://github.com/dream-num/skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/dream-num/skills/agents-md)<a href="https://agentmods.dev/instructions/dream-num/skills/agents-md"><img src="https://agentmods.dev/badge/instructions/dream-num/skills/agents-md.svg" alt="Measured on agentmods" height="20"></a>What 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.00171 | $0.00171 |
| Opus 5 | $0.00086 | $0.00086 |
| Sonnet 5 | $0.00034 | $0.00034 |
| Haiku 4.5 | $0.00017 | $0.00017 |
Grade A, and why
skills 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 3d 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.
What it actually says
- Never simplify the run-api reference descriptions of the UNIVER API. They are foundational context for LLMs to understand Univer API behavior and contracts.
- When introducing
univer-cli, keep the wording concise, elegant, and aligned with the taste of experienced mainstream developers. Avoid verbose, repetitive, or over-explained descriptions. - Unless a shell behavior is unique to
univer-cli, avoid explaining obvious shell usage. Assume the LLM is already highly proficient with shell workflows. - For complex project planning, define success criteria before the plan. The success criteria file is a short checklist of user-visible outcomes, preservation constraints, deliverables, validation signals, non-goals, and ambiguities left for the plan. It is not a plan and must not contain pack decomposition, assertion design, or execution strategy.
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.
- 3d ago First seen · 9 lines · 171 tokens per session scan A b58238606782
skills AGENTS.md is an instructions file published in the GitHub repository dream-num/skills (64 stars, last pushed 15d ago), licensed Apache-2.0. It adds 171 tokens to every session, about $0.0009 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
numera-mcp AGENTS.md
AGENTS.md instructions for vectojs/numera-mcp: This repository owns only the stdio Model Context Protocol adapter and its safe filesystem boundary. Workbook semantics remain in exact-pinned Numera Core and XLSX packages.
mcp-server-excel readme-management.instructions.md
Instructions for sbroenne/mcp-server-excel, covering readme management - quick reference, core entry documents, feature documentation, critical rules and tool & action counts must match.
mcp-server-excel extension-development.instructions.md
Instructions for sbroenne/mcp-server-excel, covering vs code extension development instructions, extension overview, changelog and changesets (critical), version management and automatic version management (unified release workflow).
mcp-server-excel copilot-instructions.md
Instructions for sbroenne/mcp-server-excel, covering github copilot instructions - excelmcp, repository map, environment, working rules and build and validation.
mcp-server-excel mcp-server-guide.instructions.md
Instructions for sbroenne/mcp-server-excel, covering mcp server development, tool pattern, errors and json, schema and descriptions and cross-surface verification.
mcp-google-sheets CLAUDE.md
Claude Code instructions for toantran201/mcp-google-sheets, covering claude.md, commands, architecture, adding or renaming a tool and auth scope is derived from enabled tools.