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/s2mon123/fep-agent-hub/agents-mdgit clone --depth 1 https://github.com/S2mon123/FEP-Agent-HubWrote 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/s2mon123/fep-agent-hub/agents-md)<a href="https://agentmods.dev/instructions/s2mon123/fep-agent-hub/agents-md"><img src="https://agentmods.dev/badge/instructions/s2mon123/fep-agent-hub/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.1 | $0.00221 | $0.00221 |
| Opus 5 | $0.00111 | $0.00111 |
| Sonnet 5 | $0.00044 | $0.00044 |
| Haiku 4.5 | $0.00022 | $0.00022 |
Grade A, and why
FEP-Agent-Hub 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.
What it actually says
FEP Agent Hub Agent Instructions
- Read
README.zh-CN.mdand the relevant file underdocs/before changing a solver workflow. - Resolve executables from
OPEN_CAE_CONFIG, environment variables, orconfigs/open-cae.local.toml. Treat public example paths as placeholders. - Keep generated models, meshes, logs, solver outputs, images, and evidence under the configured
workspace/project directory. - Do not expose arbitrary shell, arbitrary Python,
eval, or arbitrary executable tools. - Never claim solver success from file presence alone. Check process exit, logs, expected artifacts, finite fields, and case-specific physics gates.
- A capability that is intentionally unsupported must return
BLOCKEDwith a recommended next action; never fabricate an artifact. - Public files must not contain author-machine paths, commercial manuals, private models, license data, or large generated results.
- Before release, run
pytest,scripts/protocol_smoke.py, the native heat smoke, andscripts/mcp_full_validation.py.
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 · 11 lines · 221 tokens per session scan A c39e420aeadd
FEP-Agent-Hub AGENTS.md is an instructions file published in the GitHub repository S2mon123/FEP-Agent-Hub (3 stars, last pushed 22d ago), licensed MIT. It adds 221 tokens to every session, about $0.0011 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
bio-gene-to-reference-tree copilot-instructions.md
Copilot instructions for Hongda-Zhao/bio-gene-to-reference-tree, a project described as: Auditable agent skill for resolving protein queries, selecting references, and planning reproducible phylogenetic trees.
braina GEMINI.md
Instructions for brainets/braina, covering project: braina (brain interaction analysis), 1. project context & purpose, 2. commands, verify environment (all core dependencies) and run the verification test suite for frites + hoi.
research-automation CLAUDE.md
Instructions for lucafusarbassini/research-automation, covering ricet - research automation framework, project overview, claude-flow mcp, workflow habits and file organization.
shannon-prover CLAUDE.md
Claude Code instructions for SkyShannonProver/shannon-prover, covering shannon prover: claude entry point, current boundary, easycrypt environment, eval safety and current documentation.
SciCrucible CLAUDE.md
Claude Code instructions for Xinyang-Li666/SciCrucible, covering 科学知识库, 知识库结构, 可用命令, 项目目录 and 工作原则.
torchcell CLAUDE.md
Claude Code instructions for Mjvolk3/torchcell, covering vision -- the virtual cell (north star), for local configs, git worktrees, programming guide and provenance & reproducibility.