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/xfurti/leogriel/agents-mdgit clone --depth 1 https://github.com/xFurti/leogrielWrote 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/xfurti/leogriel/agents-md)<a href="https://agentmods.dev/instructions/xfurti/leogriel/agents-md"><img src="https://agentmods.dev/badge/instructions/xfurti/leogriel/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.00607 | $0.00607 |
| Opus 5 | $0.00303 | $0.00303 |
| Sonnet 5 | $0.00121 | $0.00121 |
| Haiku 4.5 | $0.00061 | $0.00061 |
Grade A, and why
leogriel 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 28 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
This repository is a pnpm workspace of TypeScript packages under packages/. The public CLI lives in packages/cli; shared behavior is split among core, manifest, lockfile, registry, link-manager, adapters, import, security, plugin-system, and project-state. Production code belongs in each package's src/, with tests in src/test/ and fixtures beside the package that consumes them. The first-party Agent Skill is in skills/leogriel/. Browser documentation and static assets live in docs/; brand artwork is in brand/; release utilities are in scripts/. Do not commit generated dist/, node_modules/, or environment files.
Build, Test, and Development Commands
pnpm installinstalls all workspace dependencies (Node.js >= 22.13, pnpm 11.x).pnpm buildbuilds every package; usepnpm build:clifor only the CLI.pnpm devwatches/runs the CLI package during development.node packages/cli/bin/leogriel.js --helpexercises the locally built executable.pnpm testruns all package test suites.pnpm test:coverageenforces repository coverage thresholds.pnpm lintruns each workspace package's TypeScript checks.
Coding Style & Naming Conventions
Use strict TypeScript and ESM imports, including .js extensions for local imports. Follow existing formatting: two-space indentation, single quotes, semicolons, trailing commas, and minimal comments. Use camelCase for variables/functions, PascalCase for types, and kebab-case filenames such as normalize-specifier.ts. Keep public exports intentional through package src/index.ts files. Prefer small modules with package ownership over adding cross-package shortcuts.
Testing Guidelines
Tests use node:test with node:assert/strict; name files *.test.ts under src/test/. Add regression tests in the package whose behavior changes, including failure and platform-sensitive cases. Run pnpm build && pnpm test before submitting. Coverage must remain at least 60% for lines, functions, and statements, and 50% for branches.
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.
- 3d ago First seen · 28 lines · 607 tokens per session scan A 62f3c51ba028
leogriel AGENTS.md is an instructions file published in the GitHub repository xFurti/leogriel (2 stars, last pushed 1mo ago), licensed MIT. It adds 607 tokens to every session, about $0.0030 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
hiveshare CLAUDE.md
Instructions for KB-perByte/hiveshare, covering hiveshare — claude.md, repo layout, build & run, key env vars (server) and naming: hive vs memory.
llm-safe-haven CLAUDE.md
Instructions for pleasedodisturb/llm-safe-haven, covering llm safe haven, what this is, project structure, tdd — non-negotiable (adopted 2026-08-17) and the contract.
kleosrules AGENTS.md
Instructions for kleosr/kleosrules, a project described as: Cursor harness pack: user rules, skills, Bash hooks, local HANDOFF memory. macOS, Linux, Windows (WSL).
finding-unknowns-skills CLAUDE.md
Claude Code instructions for Neeeophytee/finding-unknowns-skills, covering repo notes, what ships, and the gate that decides, version lives in three manifests — move them together, files that must be edited together and shipped guidance is not this file.
coding-agent-safety-gate AGENTS.md
Instructions for ASER-ho/coding-agent-safety-gate, covering agents / 代理规则, 仓库类型 / repository type and ai 代理规则 / rules for ai coding agents.
data-scientist copilot-instructions.md
Instructions for realnghon/data-scientist, covering github copilot — 项目指令：data scientist 工作流 and 共享核心 — 回答前请阅读.