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/kevinkaylie/agentnexus/agents-mdgit clone --depth 1 https://github.com/kevinkaylie/AgentNexusWrote 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/kevinkaylie/agentnexus/agents-md)<a href="https://agentmods.dev/instructions/kevinkaylie/agentnexus/agents-md"><img src="https://agentmods.dev/badge/instructions/kevinkaylie/agentnexus/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.02887 | $0.02887 |
| Opus 5 | $0.01443 | $0.01443 |
| Sonnet 5 | $0.00577 | $0.00577 |
| Haiku 4.5 | $0.00289 | $0.00289 |
Grade A, and why
AgentNexus 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 5d 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
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 5d ago First seen · 125 lines · 2,887 tokens per session scan A 7d4b83551c20
AgentNexus AGENTS.md is an instructions file published in the GitHub repository kevinkaylie/AgentNexus (9 stars, last pushed 1mo ago), with no licence file. It adds 2,887 tokens to every session, about $0.0144 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
openfused CLAUDE.md
Instructions for openfused/openfused, covering claude.md — agent instructions for openfused, what this is, first steps, install the cli and check your store.
relay AGENTS.md
AGENTS.md instructions for AgentWorkforce/relay, covering git workflow rules, never push directly to main, correct workflow, ... do work .. and stop here - let user merge.
mesh-llm AGENTS.md
AGENTS.md instructions for Mesh-LLM/mesh-llm, covering agent notes, repo overview, key docs, public website and building.
sema AGENTS.md
AGENTS.md instructions for emergent-wisdom/sema, covering repository agent guide, development workflow, vocabulary changes, vocabulary review and the improvement loop, per pattern.
agent-passport-system AGENTS.md
AGENTS.md instructions for aeoess/agent-passport-system, covering agents.md, dev environment, test before you ship, pr instructions and code style.
seedit AGENTS.md
AGENTS.md instructions for bitsocialnet/seedit, covering agents.md, purpose, surprise handling, project overview and instruction priority.