Borrowing it
Nothing to install: this file belongs to Raidriar7170/hermes-skilleval. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Raidriar7170/hermes-skilleval/main/AGENTS.mdgit clone --depth 1 https://github.com/Raidriar7170/hermes-skillevalWrote 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/raidriar7170/hermes-skilleval/agents-md)<a href="https://agentmods.dev/instructions/raidriar7170/hermes-skilleval/agents-md"><img src="https://agentmods.dev/badge/instructions/raidriar7170/hermes-skilleval/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.00363 | $0.00363 |
| Opus 5 | $0.00181 | $0.00181 |
| Sonnet 5 | $0.00073 | $0.00073 |
| Haiku 4.5 | $0.00036 | $0.00036 |
Grade A, and why
hermes-skilleval 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 8d 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
Hermes SkillEval Contributor Instructions
- Read
CONTEXT.md,README.md, the relevantdocs/v0.3/protocol, and the nearest existing implementation or docs before editing. - Keep one PR scope at a time. Do not bundle unrelated refactors or release work into protocol, benchmark, runtime, or documentation changes.
- Preserve existing CLI behavior, release gates, tests, and historical Phase 10-18 artifacts unless a later approved change explicitly updates them.
- Do not modify
src/hermes_skilleval/**,tests/**, historical phase docs, or release logic for v0.3 PR-0. - Treat the SkillRouter scored set as evaluation-only: no training, tuning, threshold selection, variant selection, or hard-negative mining on final scored labels.
- Preserve Phase 10 as deterministic offline replay evidence. Do not describe it as live-agent evidence.
- Use deterministic verifiers as the primary live-agent success judge. LLM or human review may diagnose failures but must not replace verifier outcomes.
- Keep
VALID_EVIDENCE,INVALID_EVIDENCE, andREVIEW_REQUIREDseparate from router promotion decisions such asKEEP_BASELINEandPROMOTE_CANDIDATE. - Never commit external full datasets, model checkpoints, embedding caches, credentials, raw auth files, private host details, or unsanitized agent traces.
- Mark unavailable evidence as
UNAVAILABLE; do not fabricate source, temporal, cost, token, activation, or verifier fields. - Do not claim a benchmark result, live-agent result, release decision, or public-readiness posture that was not produced by a committed command and recorded artifact.
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.
- 8d ago First seen · 28 lines · 363 tokens per session scan A 4b5224d162a8
hermes-skilleval AGENTS.md is an instructions file published in the GitHub repository Raidriar7170/hermes-skilleval (124 stars, last pushed 1mo ago), licensed MIT. It adds 363 tokens to every session, about $0.0018 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
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.