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/suhaas/earnings-edge/evalsgit clone --depth 1 https://github.com/suhaas/earnings-edgeWrote 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/suhaas/earnings-edge/evals)<a href="https://agentmods.dev/instructions/suhaas/earnings-edge/evals"><img src="https://agentmods.dev/badge/instructions/suhaas/earnings-edge/evals.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.00979 | $0.00979 |
| Opus 5 | $0.00490 | $0.00490 |
| Sonnet 5 | $0.00196 | $0.00196 |
| Haiku 4.5 | $0.00098 | $0.00098 |
Grade A, and why
evals-instructions 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 4d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 4d ago First seen · 115 lines · 979 tokens per session scan A 495be87f9529
evals-instructions is an instructions file published in the GitHub repository suhaas/earnings-edge (5 stars, last pushed 1mo ago), with no licence file. It adds 979 tokens to every session, about $0.0049 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
deer-flow AGENTS.md
AGENTS.md instructions for bytedance/deer-flow, covering agents.md, what is deerflow, service topology, repository map and commands: root vs. module.
deer-flow copilot-instructions.md
Copilot instructions for bytedance/deer-flow, covering copilot onboarding instructions for deerflow, 1) repository summary, 2) runtime and toolchain requirements, 3) build/test/lint/run - verified command sequences and a. bootstrap and install.
deer-flow CLAUDE.md
Claude Code instructions for bytedance/deer-flow: The repo's agent guidance lives in AGENTS.md so it is shared across coding agents (Claude Code, Codex, and others). Claude Code imports it below.
agents-universe CLAUDE.md
Claude Code instructions for agents-universe/agents-universe, covering agents universe — enterprise ai agent framework, project overview, monorepo layout, development commands and api (from packages/api/).
AgentEval testing.instructions.md
Guidelines for writing AgentEval unit tests.
OpenOutreach CLAUDE.md
Claude Code instructions for eracle/OpenOutreach, covering claude.md, rules, project overview, architecture and commands.