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/algorithmicsuperintelligence/openevolve/sidebar-node-logicgit clone --depth 1 https://github.com/algorithmicsuperintelligence/openevolveWhat 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.00315 | $0.00315 |
| Opus 5 | $0.00158 | $0.00158 |
| Sonnet 5 | $0.00063 | $0.00063 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
openevolve sidebar-node-logic.instructions.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.
What it actually says
-
In this program, a dataset with nodes and edges is visualized in different graphs and lists. These view modes are selectable in tabs.
-
Nodes are parametrized with meta data including program ID, island number, generation nunmber, parent ID (which is used to determine the edge connections), a metric dataset with flexible keys, a code string, a dict with prompts and more. All data except program ID are optional.
-
A sidebar shows detailed node information. Its format is the same across all view modes.
-
The sidebar in this program is designed to show up dynamically when a node is selected in one of the graphs or lists. It appears on hover of the node and hides when the node is not hovered anymore.
-
A single node can be selected to turn it "sticky". When a node is sticky, its information remains visible in the sidebar and the sidebar remains open until the user clicks in the background. Hovering another node will not change the sidebar content if a node is already sticky.
-
The selected node is highlighted with a red border and synchronized across all graphs and lists. I.e., clicking a node in a list will also highlight it in the graphs.
-
A select box #highlight-select configures a filter logic that allows to highlight multiple nodes. Nodes are highlighted with a blue shadow in the graphs and lists.
-
A select box #metric-select shows the available metrics (determined dynamically from the dataset), and the selected metric may be used in the graph creation, filter and sorting logic.
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 · 12 lines · 315 tokens per session scan A c4149e5b1ab8
openevolve sidebar-node-logic.instructions.md is an instructions file published in the GitHub repository algorithmicsuperintelligence/openevolve (7,290 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 315 tokens to every session, about $0.0016 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
seektty AGENTS.md
Instructions for Hilbert-beinghappy/seektty: This repository ships one out-of-tree DeepSeek Harness Bundle. Harness remains the only owner of Agent, Session, model, settings, permissions, Profile, plugin, and persistence state.
amp-acp AGENTS.md
Instructions for tao12345666333/amp-acp, covering agents.md, commands, architecture and code style.
roamcode AGENTS.md
Instructions for burakgon/roamcode, covering repository instructions for coding agents, public-repository safety, stable release and ota contract, releasing a stable version and ota changes.
dev-workspace AGENTS.md
Instructions for iwe-org/dev-workspace, covering agent operating manual, start of every session, the operating loop, conventions and iwe basics.
ob-1 AGENTS.md
Instructions for Overbrilliant/ob-1, covering agents.md, project index, stack, commands and key files.
kumo-coding-agent AGENTS.md
Instructions for kumo-ai/kumo-coding-agent: All instructions, routing tables, and rules are in CLAUDE.md. Read that file as the entry point for this agent.